A user-specific API returns another user's response when accessed through CloudFront.
The origin returns the correct response, and the issue occurs only through the distribution.
Which setting should be checked first?
Include the headers, cookies, or query strings that vary the response in the CloudFront cache key.
Detailed explanation
Changing object versioning does not make CloudFront distinguish request variants.
Changing object versioning does not make CloudFront distinguish request variants.
DNS delegation does not change CloudFront cache keys or existing cached objects.
DNS delegation does not change CloudFront cache keys or existing cached objects.
If a response-varying value is absent from the key, different responses can share one cached object.
If a response-varying value is absent from the key, different responses can share one cached object.
Audit-log retention does not determine CloudFront cache contents.
Audit-log retention does not determine CloudFront cache contents.
Check official documentation
Compare the following points with the official documentation.
CloudFront cache policy cache key and troubleshooting cached responsesの公式説明を確認する。
What to confirm
キャッシュキー、TTL、Invalidationの関係を説明できる。
Key points
- CloudFront cache policy
- Cache key
- CloudFront invalidation
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Variant isolation
A response-varying header, cookie, or query must distinguish the cache entry.
Key versus expiry
A correct key prevents cross-user reuse; invalidation removes an already incorrect cached object.