Question

A media company serves images through Amazon CloudFront with an Amazon S3 origin. The CloudOps team notices a low cache hit ratio and higher-than-expected S3 request costs. Investigation shows the application appends a unique tracking query string parameter (for example, ?userId=xxxx) to every image URL, though the parameter does not affect which image is returned. What is the MOST effective change to improve the cache hit ratio?

Accepted Answer

Configure the cache policy to not include any query strings in the cache key while still allowing the requests to succeed

Answer

Enable CloudFront to forward all query strings to the origin and include them in the cache key

Answer

Reduce the default TTL on the cache behavior to force more frequent revalidation with S3

Answer

Add a second CloudFront distribution and split traffic between them with Route 53 weighted routing