Does a CDN still cut S3 egress?

Teams search for “CloudFront vs S3 egress” because a cheaper CDN gigabyte looks like a win. The download still leaves a bill. Every user byte pays CDN egress. Bytes that miss the cache also pay origin fetch from the object store to the CDN. Storage is the same on both paths, so this page leaves it off.

On the default 100 GB month — $0.09 origin, $0.085 CDN, 80% hits — origin-only is $9.00. The CDN path is $8.50 of CDN egress plus $1.80 of miss-fetch, $10.30. Origin-only is $1.30 cheaper. The CDN path matches origin-only around 94.4% hits. At 95% hits the CDN path is $8.95, five cents cheaper. Paste the rates on your current price sheet. This page does not fetch provider prices.

Path	CDN / origin egress	Origin fetch	Request fees	Monthly total

Complementary to the two-provider monthly comparison (which object store) and replica vs cross-region pull (a second copy versus pulling the same bytes again) and infrequent access vs standard (retrieve fees after a class change). This page is only the internet transfer path in front of one store. The calculator is arithmetic, not advice. It does not claim a cache will hit at the rate you typed.

Common questions

Does a CDN cut S3 egress?

Not always. Every user download still pays CDN egress. Cache misses also pay origin fetch for the bytes that leave the origin toward the CDN. On a 100 GB month at $0.09 origin and $0.085 CDN, 80% hits bill $10.30 on the CDN path versus $9.00 origin-only. The CDN path matches origin-only around 94.4% hits. Paste your quoted rates; this page does not fetch provider prices.

What hit rate makes a CDN cheaper than origin egress?

The hit-rate floor is the cache-hit percentage where both paths bill the same. Below that floor, origin-only is cheaper on these rates. The page solves that volume from the rates you enter. It does not recommend turning a CDN on or off.