...
One note about the last highlighted field in the screenshot (Custom SSL certificate) - this is where the SSL cert for the custom domain appears if it was properly configured in ACM in Step 2. Although we have not selected anything in the screenshot (because we do not have SSL cert for our example domain), this field cannot be left empty - it must be set.
...
Step 3a - Create DNS record for your custom domain
Each CloudFront distribution has a unique domain name generated by AWS when the distribution is created. Create a CNAME record in your DNS provider, that points your custom domain at the unique hostname for your CloudFront distribution.
Example record:
Record name: app.mycustomdomain.com
Record type: CNAME
Record value: unique domain name generated by CloudFront
...
After creating the DNS record, allow at least 1 min for DNS to propagate and then verify if the record has been created properly using one of many DNS lookup tools like https://www.whatsmydns.net/ .
| Info |
|---|
Note: typically when making DNS changes, adding new entry propagates fast, but it’s not uncommon for modifications to an already existing record to take up to an hour or even longer. The time it takes for DNS to propagate depends on how fast your provider applies your change and TTL (Time To Live) setting for your record. Explaining the concepts behind DNS is not part of this guide but please keep in mind, if DNS lookup tools indicate different results than you expect, double check your settings and then give it at least 1 hour to propagate. |
Step 4 - Disable Caching (Optional, Troubleshooting)
...