Cloud and platforms
CloudFront vs Front Door vs Cloud CDN: Cache Keys, TTLs and Purges
In short
The costly surprise in cloudfront vs azure front door vs cloud cdn is the cache key: Google keys on the full URI, query string included, while CloudFront ignores query strings unless told otherwise. A silent origin then gets cached for a day, one to three days, or an hour, and a purge lands in seconds, minutes, or at a quota-limited rate.
What does cloudfront vs azure front door vs cloud cdn put in the cache key by default?
The key decides both the hit ratio and whether a response meant for one visitor can reach another, and the three defaults sit far apart.
On a Cloud CDN backend service, a link carrying a fresh utm_source value is a new object until you exclude that parameter. CloudFront serves the same cached file whatever follows the question mark, and warns that a high-variety header such as User-Agent in the key splits one file into thousands of copies. Values the origin needs only for logging belong in an origin request policy, which forwards them without touching the key. A missing Origin value is one of the causes behind web fonts blocked by CORS on CloudFront.
| Service | Default key | Query strings | Headers and cookies |
|---|---|---|---|
| Amazon CloudFront | Distribution domain plus URL path | Excluded until a cache policy adds all, a named list or all-except | Excluded by default; a cache policy holds up to 10 headers, 10 cookies and 10 query strings |
| Azure Front Door Standard/Premium | Request path, with query handling chosen on the route | Ignore, use all, or include or ignore named parameters; order does not matter | No header or cookie key options on the caching page |
| Google Cloud CDN (backend service) | Full request URI: protocol, host, path and query string | Include list or exclude list, never both; order does not matter | Named request headers and up to five named cookies; `Cookie` and `User-Agent` are refused |
Checked against: source 1, source 2, source 6, source 9, source 12
How long does each edge keep a file when the origin sends no Cache-Control?
CloudFront applies its Default TTL only when the origin sends no max-age, s-maxage or Expires. Without a cache policy that default is 24 hours. In the legacy settings Default TTL starts at 86,400 seconds and Maximum TTL at 31,536,000, and the maximum only bites when the origin does send a lifetime.
Front Door Standard and Premium choose a random duration between one and three days when Cache-Control is absent. Headers are read in the order s-maxage, max-age, Expires, and no expiry can exceed 366 days.
Cloud CDN is the most conservative. Default TTL and client TTL start at 3,600 seconds and max TTL at 86,400, and each can be raised to 31,622,400. Yet any expiry beyond 30 days is treated as 2,592,000 seconds by default, and an entry nobody reads for 30 days is evicted.
The Front Door range is the one I would plan around. Two edges can expire the same stylesheet a day apart, so a fix shipped under an unchanged file name can look half deployed for days unless you purge it.
Checked against: source 3, source 4, source 9, source 12, source 13
Can a response marked private or no-store still end up cached?
On CloudFront, yes, if Minimum TTL is above 0. The cache then holds the object for at least that long even when the origin says no-cache, no-store or private. With a minimum of 0, those directives are respected. The same page notes that a stale copy may be served while the origin is unreachable, and stale-if-error=0 switches that off.
Front Door does not cache private, no-cache or no-store responses, even when a Rules Engine action tries to override caching. Requests that carry an Authorization header are skipped unless the response says public, s-maxage or must-revalidate. When a response is cacheable, Front Door removes Set-Cookie before the client sees it.
Cloud CDN refuses responses carrying Set-Cookie, private or no-store in its normal modes. FORCE_CACHE_ALL ignores the Cache-Control header entirely, so a per-user page behind that mode can be stored. A nonzero CloudFront minimum TTL and that Google cache mode are the two settings to audit before an authenticated route goes behind either CDN.
How quickly does a purge take effect, and which copies does it miss?
CloudFront invalidation paths are case sensitive, and * works only as the final character. If query strings reach the origin, you must list each variant or end the path with a wildcard. Header and cookie variants, on the other hand, are all cleared together. The quota page allows 150 paths or tags per second and one wildcard invalidation per second; the pages I read give no completion time.
Front Door Standard and Premium say a purge can take up to 10 minutes to reach every point of presence. Matching ignores case and query strings, so purging one URL clears every variant of it. Wildcard domains cannot be purged directly; you name each subdomain.
A Cloud CDN invalidation takes effect in about 10 seconds, with up to 500 requests per minute per project and no cap on objects per request. Path matching skips the query string, so one variant cannot be targeted by path. The page suggests a parent path or Cache-Tag values, up to 50 tags per object and 10 per request, and admits a few caches may briefly lag.
All three vendors prefer versioned file names for routine releases. A purge also leaves browser and corporate proxy caches untouched.
Checked against: source 5, source 6, source 8, source 10, source 14
Which one can put a shield layer in front of the origin?
Of the three, only the CloudFront pages I read describe a switch for it. Origin Shield is enabled per origin in a chosen AWS Region, ideally the one closest to the origin. Every regional edge cache then fetches through it, and simultaneous misses for one object collapse to as few as one origin request. Traffic already in the shield Region skips the layer, and the feature carries its own charge.
The Front Door Standard and Premium caching page says each edge site keeps its own cache, so an origin can still see requests for content that is cached elsewhere. It describes no shield setting. The classic tier logs do record parent points of presence answering edge misses, but no customer control for them appears on the pages I read.
Cloud CDN states that an object in one cache is not copied to other caches, and it names no shield option. What it has is request coalescing, on by default, which merges concurrent fills for one cache key into a single origin request per edge node.
Checked against: source 7, source 9, source 11, source 12, source 15
Which settings break first when a cache setup moves to another cloud?
- Query parameters: list every parameter your URLs carry, and on Cloud CDN exclude the tracking ones before go-live.
- Silent origins: send an explicit
Cache-Controlinstead of inheriting 24 hours, one to three days, or one hour. - Private pages: search for a CloudFront minimum TTL above 0 and for
FORCE_CACHE_ALLon Google. - Purge scripts: CloudFront needs the exact case and every query variant, Front Door ignores both, and Cloud CDN needs tags to hit one variant.
- Origin capacity: without a shield option, size the origin for misses arriving from many edges at once.
What else do people ask?
Is this three-way comparison something people actually search for?
Barely. On 20 Nov 2026 Google Autocomplete offered nothing for the full three-way phrase, while the CloudFront and Front Door pair did complete. Each section above still reads pair by pair.
Does Azure Front Door support ETag revalidation?
No. Its caching page says only <code>Last-Modified</code> is supported as a validator, and <code>ETag</code> is not.
Sources
- AWS, Understand the cache key (CloudFront), fetched 2026-11-20
- AWS, Understand cache policies (CloudFront), fetched 2026-11-20
- AWS, Manage how long content stays in the cache (CloudFront expiration), fetched 2026-11-20
- AWS, CloudFront cache behavior settings (TTL defaults), fetched 2026-11-20
- AWS, What you need to know when invalidating paths (CloudFront), fetched 2026-11-20
- AWS, CloudFront quotas (policies and invalidations), fetched 2026-11-20
- AWS, Use Amazon CloudFront Origin Shield, fetched 2026-11-20
- AWS, Invalidate files to remove content (CloudFront), fetched 2026-11-20
- Microsoft Learn, Caching with Azure Front Door, fetched 2026-11-20
- Microsoft Learn, Purge cache for Azure Front Door, fetched 2026-11-20
- Microsoft Learn, Monitor Azure Front Door (access and classic logs), fetched 2026-11-20
- Google Cloud, Cloud CDN caching overview, fetched 2026-11-20
- Google Cloud, Cloud CDN TTL settings and overrides, fetched 2026-11-20
- Google Cloud, Cloud CDN cache invalidation overview, fetched 2026-11-20
- Google Cloud, Cloud CDN overview, fetched 2026-11-20
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Written from CloudFront, Front Door and Cloud CDN documentation read on 20 Nov 2026; no distribution, profile or backend was configured for this page, so nothing here is a measured hit ratio or purge time. Prices, Front Door (classic) settings, Media CDN, edge functions and WAF rules are left out. Found a mistake? Tell me.