Question

A media company serves static images through a CloudFront distribution backed by an S3 origin. Monitoring shows a low cache hit ratio and higher-than-expected origin request volume, driving up S3 GET costs. Investigating the origin responses, the SysOps administrator finds that S3 returns objects with a Cache-Control: max-age=60 header, and the distribution's cache behavior is configured to use origin cache headers with a Minimum TTL of 0, Maximum TTL of 60, and Default TTL of 0. The images rarely change. What is the MOST effective change to increase the cache hit ratio?

Accepted Answer

Increase the Minimum TTL and Maximum TTL on the cache behavior (and adjust the S3 Cache-Control max-age) so objects remain cached longer at edge locations.

Answer

Enable query string forwarding on the cache behavior so that CloudFront caches each variation separately.

Answer

Change the origin from S3 to a custom origin using an Application Load Balancer to reduce origin request latency.

Answer

Create an invalidation for /* to force CloudFront to refresh and cache the objects.