1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Just closing the loop on this one. It appears there was a restriction in Route53 console that was preventing Gov Cloud region selection when creating alias records. My client opened a support ticket and the restriction/bug in the console was quickly resolved by AWS Support. Once again we are able to create/modify public Route53 alias records to Gov-Cloud resources.
répondu il y a un an
Contenus pertinents
- demandé il y a un an
- demandé il y a 7 mois
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
The way this has always previously worked, is from the Route53 Create Record form you could choose your resource type, choose gov-west or gov-east, and then paste in the DNS record for the Gov resource. The list of resources for the respective gov-west or gov-east would not populate (because they would be under a separate gov account) but you could choose region gov-west or gov-east, and then paste in resource records. Now gov-east and gov-west are not in the region dropdown, and if you choose a different region to paste in the DNS record you will get error that it is not a valid resource for that region.