Understanding Cdn pricing requires looking beyond the headline transfer fee. Most providers split billing into data egress, HTTP/HTTPS requests, invalidation actions, and optional edge compute. For teams buying through CnCloud, an AWS Advanced Tier Services Partner, the goal is to make these components predictable rather than reacting to an unexpected invoice.
aws cdn pricing
Cdn pricing for AWS CloudFront is built from several separate charges. The largest is usually data transfer out to the internet, but HTTP/HTTPS requests, invalidation requests, and Lambda@Edge invocations can add up quickly for dynamic or API-heavy workloads. The per-GB egress rate changes by region, so serving users from North America may differ from serving users in Asia Pacific.
| Pricing component | What triggers it | Why it matters |
|---|---|---|
| Data transfer out | GB egress to end users | Regional rate differences can raise cost |
| HTTP/HTTPS requests | Every viewer request | Low cache hit rates increase volume |
| Invalidation requests | Clearing cached objects | Frequent purges add fees |
| Lambda@Edge | Edge function invocations | Adds compute cost per request |
To reduce these costs, focus on cache hit ratio first. A higher ratio means fewer origin fetches and lower request and egress overhead. Next, separate dynamic and static content; dynamic paths often bypass cache and trigger higher request-based billing. Finally, group invalidation calls or use versioned file names instead of purging entire distributions, which can cut invalidation fees.
Practical CDN cost control also depends on how you pay. USDT top-up is credited instantly, while corporate or bank transfer typically arrives in 1-2 business days. Combining right-sizing, architecture optimization, and reseller discounts can reduce overall cloud bills by up to ~30%. Compare the full cost stack, not just the per-GB headline, before choosing a CDN setup.