如何解决如何用指向A CloudFront分配的简单A记录替换策略记录而不会造成流量中断?
我的第一个问题是,执行此操作的最佳方法是什么?在我看来,不中断流量的唯一方法是通过AWS CLI,但是如果有更简单的方法,我将不胜感激!如果使用CLI来执行此操作,则以下命令会遇到问题:
aws route53 change-resource-record-sets --hosted-zone-id XXXXXXXXXXXX --change-batch file://update-record.json
update-record.json
包含以下内容:
{
"Comment": "Swaps the Policy Record for a simple routing policy","Changes": [
{
"Action": "UPSERT","ResourceRecordSet": {
"Name": "www.example.com","Type": "A","AliasTarget": {
"HostedZoneId": "XXXXXXXXXXXX","DNSName": "xxxxxxxxxxxxx.cloudfront.net","EvaluateTargetHealth": false
}
}
}
]
}
我得到的错误是:
An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: [Tried to create an alias that targets xxxxxxxxxxxxx.cloudfront.net.,type A in zone XXXXXXXXXXXX,but the alias target name does not lie within the target zone,Tried to create an alias that targets xxxxxxxxxxxxx.cloudfront.net.,but that target was not found]
该帐户中记录的托管区域ID正确,分发DNS名称也正确。记录名称www.example.com也存在于帐户中。该发行版的备用域名(CNAME)为www.example.com。
我还尝试过将更改作为删除和创建操作,而不是upsert
:
{
"Comment": "Swaps the Policy Record for a simple routing policy","Changes": [
{
"Action": "DELETE","ResourceRecordSet": {
"Name": "www.example.com.","TrafficPolicyInstanceId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}
},{
"Action": "CREATE","EvaluateTargetHealth": false
}
}
}
]
}
分两个步骤进行操作会产生相同的错误消息。
解决方法
Route 53中的每个域和子域均被视为“托管区域”,因此具有“托管区域ID”。但是,尽管change-resource-record-sets documentation涉及面很广,但对于指向CloudFront发行版的Alias记录还是不太清楚。我不得不更深入地研究,并专门研究有关AliasTarget的文档。在那里,文档指出:
Specify Z2FDTNDATAQYW2. This is always the hosted zone ID when you create an alias record that routes traffic to a CloudFront distribution.
这意味着即使我试图在托管区域中创建ID为XXXXXXXXXXXX
的Alias记录,该ID也用于 any 指向的Alias记录任何 CloudFront发行版均为Z2FDTNDATAQYW2
。将update-record.json
更改为以下工作:
{
"Comment": "Swaps the Policy Record for a simple routing policy","Changes": [
{
"Action": "DELETE","ResourceRecordSet": {
"Name": "www.example.com.","Type": "A","TrafficPolicyInstanceId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}
},{
"Action": "CREATE","AliasTarget": {
"HostedZoneId": "Z2FDTNDATAQYW2","DNSName": "xxxxxxxxxxxxx.cloudfront.net","EvaluateTargetHealth": false
}
}
}
]
}
以change-resource-record-set
的方式进行操作可防止流量中断,例如:
Change batches are considered transactional changes. Route 53 validates the changes in the request and then either makes all or none of the changes in the change batch request. This ensures that DNS routing isn't adversely affected by partial changes to the resource record sets in a hosted zone.
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。