A public-works status site caches road-closure JSON at CloudFront w…

Question

A public-works status site caches road-closure JSON at CloudFront with a multi-hour TTL. After storms, citizens see stale detours for too long even though origin updates quickly. Which cache-effectiveness change best balances performance and freshness?

Accepted Answer

Shorten TTLs (and use cache policies/invalidations or versioned objects as needed) for rapidly changing closure data so edge performance remains while citizens receive timely updates — Caching yesterday’s flooded bridge is how you send drivers into the river. Keep the edge for speed, but shrink TTLs—and invalidate or version when closures flip—so the map stays honest.

Answer

Disable CloudFront entirely and serve every request from a single Origin EC2 host in one AZ

Answer

Raise the TTL to one week so edge caches almost never revalidate

Answer

Cache closure documents only in Amazon Glacier Deep Archive for fastest citizen reads

A public-works status site caches road-closure JSON at CloudFront with a multi-hour TTL. After storms, citizens see stale detours for too long even though origin updates quickly. Which cache-effectiveness change best balances performance and freshness?

Short Explanation

Full Explanation