Introduction
One of the purposes of using CloudFront is to reduce the number of requests that your origin server must respond to directly. This reduces the load on your origin server and also reduces latency because more objects are served from CloudFront edge locations, which are closer to your users.
Performance improvements
You can improve performance by increasing the proportion of your viewer requests that are served from CloudFront edge caches instead of going to your origin servers for content; that is, by improving the cache hit ratio for your distribution.
This can be done by doing any of the following:
1. Increase the TTL of your objects
2. Configure the distribution to forward only the required query string parameters, cookies or request headers for which your origin will return unique objects.
3. Remove Accept-Encoding header when compression is not needed
4. Serving Media Content by using HTTP
CloudFront Distribution support websocket protocol and HTTP protocol with Following HTTP methods
- GET
- POST
- PUT
- DELETE
- HEAD
- OPTIONS
- PATCH
Cloudfront Origions
- Using Amazon S3 Buckets for Your Origin
- Using Amazon S3 Buckets Configured as Website Endpoints for Your Origin
- Using a MediaStore Container or a MediaPackage Channel for Your Origin
- Using Amazon EC2 or Other Custom Origins
- Using CloudFront Origin Groups
- Adding CloudFront When You’re Already Distributing Content from Amazon S3
- Moving an Amazon S3 Bucket to a Different Region