If the X-Cache header is "Miss from cloudfront," then the request was retrieved from the origin and wasn't served by the cache.

Review the Cache-Control header in the response. If the value for Cache-Control is "no-cache" or "no-store," then the header is directing CloudFront to not cache the response, or to verify with the origin before returning a cached response. This directive supersedes the Maximum TTL and Default TTL CloudFront settings.

Note: Responses that aren't from the cache won't have an Age header.

CloudFront is caching error responses

By default, CloudFront forwards error responses from the origin to the client. Additionally, CloudFront caches the origin's error response for 5 minutes (300 seconds).

If the error response from the origin contains a Cache-Control header, CloudFront caches the error according to the relevant TTL instead of the default 5 minutes. CloudFront doesn't cache its own error responses, unless specified otherwise in a custom error response.

To determine whether the error response is from the origin or Cloudfront, check the Server header. To determine whether the error is a cached response, check the Age header—a cached response includes an Age header.

The following example is an error from an Amazon Simple Storage Service (S3) origin that's a cached response: