AWS AmazonCloudFront documentation change
Summary
Clarified DNS configuration requirements for apex domains, added DNS propagation details, and expanded list of DNS provider documentation links
Security assessment
Changes focus on DNS configuration clarity and documentation references. While proper DNS configuration is important for security, there's no evidence this addresses a specific vulnerability. The changes improve operational accuracy rather than mitigate security risks.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/managed-cloudfront-certificates.md b/AmazonCloudFront/latest/DeveloperGuide/managed-cloudfront-certificates.md index 24218481e..0ff05dd89 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/managed-cloudfront-certificates.md +++ b//AmazonCloudFront/latest/DeveloperGuide/managed-cloudfront-certificates.md @@ -155 +155 @@ You can choose **Check certificate status** to verify when ACM issues the certif -Update your DNS records to route traffic from each domain to the CloudFront routing endpoint. You can have multiple domain names, but they must resolve to this endpoint. +Update your DNS records to route traffic from each domain to the CloudFront routing endpoint. You can have multiple domain names, but they must all resolve to this endpoint. @@ -177 +177 @@ Update your DNS records to route traffic from each domain to the CloudFront rout - * For apex/root domains – Create an ALIAS record (Route 53) or similar functionality from your DNS provider that allows apex domain redirection. For example, in Route 53: + * For apex/root domains – This requires a unique DNS configuration, because standard CNAME records can’t be used at the root or apex domain level. Because most DNS providers don’t support ALIAS records, we recommend creating an ALIAS record in Route 53. For example: @@ -189 +189 @@ Update your DNS records to route traffic from each domain to the CloudFront rout - 3. Verify that the DNS change has propagated. (This can take 24-48 hours.) Use a tool like `dig` or `nslookup`. + 3. Verify that the DNS change has propagated. (This usually happens when the TTL is expired. Sometimes it can take 24-48 hours.) Use a tool like `dig` or `nslookup`. @@ -194 +194,20 @@ Update your DNS records to route traffic from each domain to the CloudFront rout - 3. Return to the CloudFront console and choose **Submit**. This returns you to the distribution tenant page. When your domain is active, CloudFront updates the domain status to indicate that your domain is ready to serve traffic. + 3. Return to the CloudFront console and choose **Submit**. When your domain is active, CloudFront updates the domain status to indicate that your domain is ready to serve traffic. + + + + +For more information, see the documentation for your DNS provider: + + * [Cloudflare](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/) + + * [ClouDNS](https://www.cloudns.net/wiki/article/9/) + + * [DNSimple](https://support.dnsimple.com/categories/dns/) + + * [Gandi.net](https://www.gandi.net/) + + * [GoDaddy](https://www.godaddy.com/help/manage-dns-records-680) + + * [Google Cloud DNS](https://cloud.google.com/dns/docs/records) + + * [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-to-change-dns-for-a-domain/)