Question

A media company serves a large catalog of static images and video thumbnails through Amazon CloudFront, backed by an S3 origin in us-east-1. The site has grown into a global audience, and CloudWatch metrics show the origin fetch rate (requests reaching S3) has climbed steadily as viewers in more regions request the same popular assets simultaneously. Finance flags rising S3 GET request charges and data transfer out to CloudFront. The cache TTLs are already tuned appropriately, and the assets rarely change. The team wants to reduce the number of duplicate origin requests for the same objects across CloudFront's many regional edge caches without changing the application or the S3 bucket structure. Which action best improves the cache efficiency and reduces origin load?

Accepted Answer

Enable CloudFront Origin Shield in a Region close to the S3 origin so all regional edge caches consolidate origin fetches through a single additional caching layer.

Answer

Increase the CloudFront default and maximum TTLs to the maximum allowed values so objects are evicted from edge caches less frequently.

Answer

Add an Amazon ElastiCache for Redis cluster in front of the S3 bucket to cache frequently requested objects and reduce GET requests.

Answer

Replicate the S3 bucket to multiple Regions with Cross-Region Replication and use a Lambda@Edge function to route each edge to the nearest replica bucket.