Using HTTPS with CloudFront
For web distributions, you can configure CloudFront to require that viewers use HTTPS to request your objects, so connections are encrypted when CloudFront communicates with viewers. You also can configure CloudFront to use HTTPS to get objects from your origin, so connections are encrypted when CloudFront communicates with your origin.
If you configure CloudFront to require HTTPS both to communicate with viewers and to communicate with your origin, here's what happens when CloudFront receives a request for an object. The process works basically the same way whether your origin is an Amazon S3 bucket or a custom origin such as an HTTP/S server:
A viewer submits an HTTPS request to CloudFront. There's some SSL/TLS negotiation here between the viewer and CloudFront. In the end, the viewer submits the request in an encrypted format.
If the object is in the CloudFront edge cache, CloudFront encrypts the response and returns it to the viewer, and the viewer decrypts it.
If the object is not in the CloudFront cache, CloudFront performs SSL/TLS negotiation with your origin and, when the negotiation is complete, forwards the request to your origin in an encrypted format.
Your origin decrypts the request, encrypts the requested object, and returns the object to CloudFront.
CloudFront decrypts the response, re-encrypts it, and forwards the object to the viewer. CloudFront also saves the object in the edge cache so that the object is available the next time it's requested.
The viewer decrypts the response.
For information about how to require HTTPS between viewers and CloudFront, and between CloudFront and your origin, see the following topics.
- Requiring HTTPS for Communication Between Viewers and CloudFront
- Requiring HTTPS for Communication Between CloudFront and Your Custom Origin
- Requiring HTTPS for Communication Between CloudFront and Your Amazon S3 Origin
- Using Alternate Domain Names and HTTPS
- Supported Protocols and Ciphers
- Charges for HTTPS Connections