Using Alternate Domain Names and HTTPS
By default, you can deliver your content to viewers over HTTPS by using your CloudFront
distribution domain name in your URLs, for example,
https://d111111abcdef8.cloudfront.net/image.jpg. For more information, see Requiring HTTPS for Communication Between
Viewers and CloudFront.
If you want your viewers to use HTTPS and you want to use your own domain name in the URLs
for your objects (for example,
https://www.example.com/image.jpg), you need to
perform several additional steps, as explained in this topic.
When you add a certificate to your distribution, CloudFront immediately propagates the certificate to all of its edge locations. As new edge locations become available, CloudFront will propagate the certificate to those locations, too. You can't restrict the edge locations that CloudFront propagates the certificates to.
- Choosing How CloudFront Serves HTTPS Requests
- Requirements for Using SSL/TLS Certificates with CloudFront
- Limits on Using SSL/TLS Certificates with CloudFront (HTTPS Between Viewers and CloudFront Only)
- Configuring Alternate Domain Names and HTTPS
- Determining the Size of the Public Key in an SSL/TLS Certificate
- Increasing the Limit for SSL/TLS Certificates
- Rotating SSL/TLS Certificates
- Reverting from a Custom SSL/TLS Certificate to the Default CloudFront Certificate
- Switching from a Custom SSL/TLS Certificate with Dedicated IP Addresses to SNI