- Newest
- Most votes
- Most comments
If your DNS provider does not support Alias/ANAME records, you cannot use CloudFront for your root/apex record (e.g., example.com). However, you can use it for any subdomain (e.g., www.example.com), by creating the record itself as a CNAME. A key difference between A records and CNAME records is that an A record accepts an IPv4 address as the value for its record, whereas CNAME (or canonical name) accepts a domain as its value. If you disable the CloudFront distribution, there would be downtime as you're disabling it. Other changes are gracefully rolled out to the edge locations, so you might experience different behavior depending on your location in the world.
https://stackoverflow.com/questions/63913805/using-a-record-or-cname-for-cloud-front-distribution
CloudFront distribution name (<ID>.cloudfront.net) resolved IPs are dynamic.
For other DNS providers, you can configure a CNAME as per How can I configure CloudFront to serve my content using an alternate domain name over HTTPS?.
With Route 53, you can setup an Alias record. Alternatively, check with your DNS provider if they have a similiar feature to R53 alias record. Some providers do and called it CNAME flattening.
Hi Mike, i'm checking with cloudflare just to ensure that i will be able to use the CNAME Flattening because I dont want my dns to be transfert to cloudflare if i decide to go that way.
Hello,
You should now be able to create an alias record in your DNS zone’s advanced tab to target your Cloudfront distribution.
Thank you for using Lightsail, Leslie
Relevant content
- asked 3 years ago
- asked 3 years ago
- asked 5 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
thanks for you reply