Why is my CloudFront CDN still showing the old version of my index html file even after I uploaded a new one?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Why is my CloudFront CDN still showing the old version of my index html file even after I uploaded a new one?
1 real search · 1 real-search pass
AWS CloudFront S3 old index.html still served after upload cache invalidation default root object cache behavior documentationGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
AWS CloudFront S3 old index.html still served after upload cache invalidation default root object cache behavior documentation Google ↗
- Push updated Amazon S3 content from CloudFront · repost.aws
- Controlling how long Amazon S3 content is cached by Amazon CloudFront · docs.aws.amazon.com
- Manage how long content stays in the cache (expiration) · docs.aws.amazon.com
- What you need to know when invalidating paths · docs.aws.amazon.com
- Amazon CloudFront · docs.aws.amazon.com
- Host Single Page Applications (SPA) with Tiered TTLs on CloudFront and S3 · aws.amazon.com
- Amazon S3 + CloudFront: A Better Way to Deliver Static Content · builder.aws.com