能否通过CloudFormation或Terraform在AWS中创建Route53流量策略并实现区域流量均分？

Absolutely! Both CloudFormation and Terraform fully support creating Route 53 Traffic Policies to implement that 50%/50% cross-region traffic split. I’ll show you step-by-step examples for both tools below.

Using CloudFormation for Route 53 50/50 Traffic Routing #

You’ll need three key resources here: a AWS::Route53::TrafficPolicy to define the weighted routing logic, a AWS::Route53::TrafficPolicyInstance to attach that policy to your hosted zone and record, plus your existing hosted zone (assuming you already have that set up).

Here’s a complete template snippet that implements the 50/50 split:

AWSTemplateFormatVersion: '2010-09-09'
Resources:
  # Define the weighted traffic policy (50%/50% split)
  CrossRegionTrafficPolicy:
    Type: AWS::Route53::TrafficPolicy
    Properties:
      Name: CrossRegion5050Policy
      Document: |
        {
          "AWSPolicyFormatVersion": "2015-10-01",
          "RecordType": "A",
          "StartRule": "WeightedSplit",
          "Rules": {
            "WeightedSplit": {
              "Type": "Weighted",
              "Items": [
                {
                  "Weight": 50,
                  "EndpointReference": "us-east-1-Endpoint"
                },
                {
                  "Weight": 50,
                  "EndpointReference": "eu-west-1-Endpoint"
                }
              ]
            }
          },
          "Endpoints": {
            "us-east-1-Endpoint": {
              "Type": "IPAddress",
              "Value": "1.2.3.4" # Replace with your us-east-1 origin IP
            },
            "eu-west-1-Endpoint": {
              "Type": "IPAddress",
              "Value": "5.6.7.8" # Replace with your eu-west-1 origin IP
            }
          }
        }

  # Attach the policy to your hosted zone and create the record
  TrafficPolicyInstance:
    Type: AWS::Route53::TrafficPolicyInstance
    Properties:
      HostedZoneId: !Ref YourHostedZoneId # Replace with your hosted zone ID
      Name: "app.yourdomain.com" # Replace with your desired record name
      TTL: 300
      TrafficPolicyId: !Ref CrossRegionTrafficPolicy
      TrafficPolicyVersion: !GetAtt CrossRegionTrafficPolicy.LatestVersion

Key Notes: #

• The Document property defines the routing logic: we use a Weighted rule with two endpoints each assigned a weight of 50, ensuring equal traffic distribution.
• Replace the IP addresses, hosted zone ID, and record name with your actual resources.
• If you’re routing to other endpoint types (like ELBs), adjust the Endpoint type in the policy document (e.g., ElasticLoadBalancing instead of IPAddress).

Using Terraform for Route 53 50/50 Traffic Routing #

In Terraform, you’ll use the aws_route53_traffic_policy and aws_route53_traffic_policy_instance resources to achieve the same result. Here’s a working example:

# Define the weighted traffic policy
resource "aws_route53_traffic_policy" "cross_region_5050" {
  name        = "CrossRegion5050Policy"
  document    = jsonencode({
    AWSPolicyFormatVersion = "2015-10-01"
    RecordType             = "A"
    StartRule              = "WeightedSplit"
    Rules = {
      WeightedSplit = {
        Type  = "Weighted"
        Items = [
          {
            Weight             = 50
            EndpointReference  = "us-east-1-Endpoint"
          },
          {
            Weight             = 50
            EndpointReference  = "eu-west-1-Endpoint"
          }
        ]
      }
    }
    Endpoints = {
      "us-east-1-Endpoint" = {
        Type  = "IPAddress"
        Value = "1.2.3.4" # Replace with your us-east-1 origin
      }
      "eu-west-1-Endpoint" = {
        Type  = "IPAddress"
        Value = "5.6.7.8" # Replace with your eu-west-1 origin
      }
    }
  })
}

# Attach the policy to your hosted zone
resource "aws_route53_traffic_policy_instance" "cross_region_instance" {
  hosted_zone_id       = "Z0123456789ABCDEFGHIJ" # Replace with your hosted zone ID
  name                 = "app.yourdomain.com"
  ttl                  = 300
  traffic_policy_id    = aws_route53_traffic_policy.cross_region_5050.id
  traffic_policy_version = aws_route53_traffic_policy.cross_region_5050.version
}

Key Notes: #

• We use jsonencode to cleanly define the traffic policy document in HCL.
• Just like with CloudFormation, adjust the endpoint types, IPs, hosted zone ID, and record name to match your infrastructure.
• Terraform will automatically manage the policy versioning for you when you update the document.

Both approaches will create a Route 53 traffic policy that routes 50% of your traffic to each specified region. You can verify the setup in the Route 53 console by checking the traffic policy instance and testing the record with tools like dig or nslookup to confirm the split is working.

内容的提问来源于stack exchange，提问作者DevBabai