Our AWS CloudFront CDN is serving stale cache content after every deployment, how can I configure invalidation rules properly without breaking our single-page app?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Our AWS CloudFront CDN is serving stale cache content after every deployment, how can I configure invalidation rules properly without breaking our single-page app?
2 real searches · 1 real-search pass
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 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
AWS CloudFront invalidation paths wildcard cache policy SPA index.html cache-control documentation Google ↗
AWS CloudFront cache behavior error response 403 404 SPA routing S3 documentation Google ↗
- Determine which paths to invalidate · docs.aws.amazon.com
- What you need to know when invalidating paths · docs.aws.amazon.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
AWS CloudFront invalidation paths wildcard cache policy SPA index.html cache-control documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
AWS CloudFront cache behavior error response 403 404 SPA routing S3 documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |