routing-traffic-with-route53-and-cloudfront

You need to add the custom domain to CloudFront alternate domain names, request an ACM certificate in us-east-1, and create Route 53 alias A/AAAA records pointing to the distribution domain for HTTPS traffic.

CloudFront custom domains require an ACM certificate in us-east-1 because CloudFront is a global service. You must request and validate the certificate there before attaching it to the distribution for secure TLS.

To configure IPv6 traffic, create AAAA alias records in Route 53 pointing to the CloudFront distribution. This requires IPv6 to be enabled on the distribution alongside the standard A alias records.

The correct order is to first add the custom domain to CloudFront alternate domain names, then request and validate the ACM certificate, and finally create the Route 53 alias A/AAAA records to ensure HTTPS readiness.

Yes, by verifying distribution status and validating inputs like domain format before applying changes. You use AWS CLI to UPSERT alias records and monitor Route 53 change propagation using DNS lookup tools to ensure reliable routing.

CloudFront alternate domain names must be added to the distribution before creating Route 53 records. The failure often indicates the ACM certificate validation is pending or the distribution status has not fully deployed.