Data transfer out cost explained: the cloud's most surprising charge

Quick answer

Data transfer out (egress to the internet) is priced per GB, tiered so the rate falls as volume rises, and it varies by region (a few cents per GB in North America and Europe, more in Asia, South America, and Oceania). Inbound transfer is almost always free; the surprise is outbound. Cross-region and cross-AZ transfer also cost, and traffic to the internet costs most. To cut egress, cache with a CDN so bytes serve from the edge, keep traffic within a region and AZ where possible, compress responses, and watch cross-region replication and multi-cloud data movement.

Data transfer out is the cloud charge that catches almost everyone eventually. Compute and storage are intuitive, you provisioned them, but egress bills for something invisible: bytes leaving the cloud to reach your users. Inbound is free, so it is easy to forget outbound is not, until a traffic-heavy service or a big data export produces a bill nobody budgeted for. Understanding egress is essential to predictable cloud cost.

How egress pricing works

Transfer type	Typical cost
Inbound (to the cloud)	Usually free
Out to the internet	Per GB, tiered down at volume, varies by region
Cross-region	Per GB, cheaper than internet egress but not free
Cross-AZ (within region)	Small per-GB charge on many services
Same-AZ / within-service	Often free or minimal

Internet egress is the priciest and most common surprise: a few cents per GB in cheap regions, more in expensive ones, tiered so the per-GB rate falls as monthly volume rises. Cross-region transfer (moving data between regions) is cheaper than internet egress but still adds up, as covered in cross-region replication cost. Cross-AZ transfer within a region is small per GB but can accumulate for chatty services.

Why egress surprises people

Egress is invisible until the bill: you do not provision it, you do not see it accumulating, and it scales with traffic you may not directly control (users downloading, APIs responding, data syncing). A viral moment, a large export, or a misconfigured sync can spike egress fast. And because it is buried across services (it shows up on your compute, storage, CDN, and load balancer lines), it is hard to see as one number. That is why egress is the classic surprise-bill component alongside monitoring.

How to cut data transfer out

The biggest lever is caching: put a CDN in front of cacheable content so bytes serve from the edge (often cheaper than origin egress, and the origin fill from AWS to CloudFront is free). Keep traffic within a region and availability zone where possible, since cross-region and cross-AZ transfer add charges, so co-locate services that talk to each other a lot. Compress responses so fewer bytes cross the wire. Serve large downloads from object storage through a CDN rather than direct. And watch multi-cloud data movement, egress between clouds is billed on the way out of each.

Making egress predictable

Estimate egress from your traffic: total GB out per region times the regional rate, remembering the volume tiers. Watch the hidden contributors, cross-AZ chatter between microservices, replication, log shipping, and backups leaving the region. Because egress scales with traffic and often with per-customer activity, fold it into cost per customer so it does not erode margin silently. Model your architecture's data flows against the resource catalog so egress is a planned cost, not a surprise.

FAQ

What is data transfer out cost?

The charge for data leaving the cloud, egress, priced per GB and tiered so the rate falls as monthly volume rises, varying by region (a few cents per GB in North America and Europe, more in Asia, South America, and Oceania). Inbound transfer to the cloud is almost always free; the surprise is outbound. Traffic to the internet costs most, with cross-region and cross-AZ transfer also billed.

Why is data transfer out so expensive?

Because clouds price internet egress per GB and it scales with traffic you may not directly control (users downloading, APIs responding, data syncing). It is invisible until the bill since you do not provision it, and it hides across your compute, storage, CDN, and load balancer lines rather than showing as one number. A traffic spike or large export can inflate it fast.

Is inbound data transfer free?

Almost always, yes. Cloud providers generally do not charge for data transfer into the cloud (inbound), which is why the surprise is always outbound. This asymmetry, free in, paid out, is deliberate: it makes moving data into the cloud easy and moving it out costly, which is also part of why egress is a factor in avoiding lock-in and planning multi-cloud architectures.

How do I reduce data transfer out cost?

Cache with a CDN so bytes serve from the edge instead of your origin, keep traffic within a region and availability zone where possible (co-locate chatty services since cross-region and cross-AZ transfer cost), compress responses so fewer bytes cross the wire, serve large downloads through a CDN rather than direct from storage, and watch multi-cloud data movement and replication. Caching is usually the biggest lever.

Does cross-AZ traffic cost money?

Often yes, a small per-GB charge on many services for data moving between availability zones within a region. It is far cheaper than internet egress, but for chatty microservice architectures that send a lot of traffic across AZs, it accumulates. Co-locating services that communicate heavily in the same AZ (while keeping the redundancy you need) reduces this cross-AZ transfer cost.

Does C3X help predict data transfer cost?

C3X prices infrastructure from your Terraform against a live catalog, surfacing the resources that drive egress (CDNs, load balancers, cross-region setups) before deploy. Exact egress depends on runtime traffic, but seeing the data-flow architecture and its region footprint upfront helps you anticipate egress and design to minimize it, rather than discovering it as a surprise on the bill.

What to do next

Plan your data flows and egress before deploy. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.