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.
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?.
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
- demandé il y a un an
- Réponse acceptéedemandé il y a 5 mois
- Comment résoudre l'erreur « CloudFront wasn't able to connect to the origin » (« CloudFront n'a pas pu se connecter à l'origine ») ?AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 10 mois
- Quelles informations dois-je communiquer à AWS Support pour diagnostiquer les problèmes de latence liés à distribution web de CloudFront ?AWS OFFICIELA mis à jour il y a 6 mois
- AWS OFFICIELA mis à jour il y a 2 ans