AWS egress negotiation: cutting data-transfer cost.
Egress is the most overlooked line on a large AWS bill — it accumulates in per-gigabyte increments across thousands of workloads, yet at scale it becomes one of the most negotiable charges AWS levies. This note maps the rate tiers, the inter-AZ and inter-region traps, the free-egress-on-exit rule, and the architecture and contract levers that cut petabyte-scale egress 35 to 65 percent.
Internet egress lists at $0.05–$0.09/GB, but the bill is rarely what teams think. Internal cross-AZ and NAT-gateway charges usually dwarf customer-facing egress, and both are cut by architecture, not contract. Fix placement first, then negotiate a committed-volume waiver on what remains — petabyte-scale accounts routinely take 35–65% off, and the free-egress-on-exit rule has stripped away the switching cost AWS once relied on.
01 Key findings
Egress hides in small increments. It accrues per gigabyte across thousands of workloads and is the AWS cost least often attributed to the workloads that generate it — which is exactly why it goes unmanaged until the bill is broken down by transfer type.
Internal traffic often dominates. Cross-AZ transfer at $0.01/GB each way and NAT-gateway processing at roughly $0.045/GB usually exceed the customer-facing internet egress everyone assumes is the problem. These are reduced by placement and VPC endpoints, not negotiation.
At scale, egress is highly negotiable. Petabyte-scale accounts routinely negotiate 35–65% off through committed-volume waivers priced against a credible forecast — but AWS discounts what you commit, so the forecast must follow the architecture fixes, not precede them.
Free egress on exit has changed the calculus. Since 2024, AWS waives transfer-out fees for customers fully leaving the platform. The cost of leaving is now engineering effort, not a transfer penalty — which strengthens any renewal position.
Architecture first, contract second. Negotiating a waiver on egress you could have eliminated through better placement is paying to discount waste. A clean attribution model feeds both the engineering backlog and the negotiation.
02 Egress rate tiers
AWS charges for data leaving its network to the public internet on a declining per-gigabyte scale, with the first 100 GB per month free across most services and inbound transfer free entirely. Rates vary by source region — US and EU regions are cheapest, while South America and parts of Asia Pacific run materially higher. First-100-GB-free US East internet-egress tiers:
| Monthly egress (US East) | Per-GB rate | Effective cost at volume |
|---|---|---|
| First 100 GB | $0.00 | Free |
| Up to 10 TB | $0.09 | $900 per 10 TB |
| Next 40 TB | $0.085 | $3,400 per 40 TB |
| Next 100 TB | $0.07 | $7,000 per 100 TB |
| Over 150 TB | $0.05 | $50,000 per PB |
Even at the deepest published tier of $0.05/GB, a petabyte of monthly internet egress lists at $50,000 — $600,000 per year before any regional premium. For a media, gaming, or data-distribution business, egress can exceed compute as the largest AWS line.
03 Inter-AZ and inter-region traps
The egress that surprises teams is not internet egress; it is transfer inside the architecture. The destination determines the rate more than the volume does, and traffic that crosses an Availability Zone or region boundary accrues cost on every byte — charges that are invisible until the bill is analyzed by transfer type. NAT gateways compound this: they add a per-gigabyte processing fee of roughly $0.045 on top of the egress, effectively double-counting at the gateway.
| Destination | Typical rate (per GB) | Reduction approach |
|---|---|---|
| Public internet | $0.05 to $0.09 | Edge caching, committed waiver |
| Cross-region | $0.02 | Co-locate dependent services |
| Cross-AZ | $0.01 each way | Consolidate chatty services |
| Same-AZ, private IP | $0.00 | Default for co-located compute |
| To CloudFront origin | $0.00 | Route distribution via edge |
Routing internet egress through Amazon CloudFront often lowers the effective rate: data-out pricing is lower than direct EC2 or S3 egress at volume, and CloudFront-to-origin transfer is free. For high-volume content delivery, moving egress behind CloudFront and then committing to a CloudFront private pricing agreement can cut the blended transfer rate by 30 to 50 percent before any account-level negotiation. Model the CloudFront path first.
04 Cost at petabyte scale
The declining scale rewards volume, but shallowly: the deepest published tier is only about 44% below the first-10TB rate. That is why negotiation matters more than tier progression at scale — the published curve alone does not get a petabyte-scale account to a defensible unit price. Published US East internet-egress rate by tier:
For predictable, steady egress to a fixed destination, AWS Direct Connect replaces internet egress with a dedicated private link billed around $0.02/GB or less plus a port-hour charge. The economics favor it once sustained egress to one destination passes a few hundred terabytes a month — the lower per-gigabyte rate overtakes the port and circuit cost, and performance stabilizes.
05 The egress lock-in trap
Egress is the charge that most shapes cloud lock-in, because moving large datasets out of a provider has historically carried a transfer-fee penalty that discouraged leaving. In a multi-cloud estate the egress cost of shuttling data between providers for processing can quietly exceed the compute saving the second provider was chosen for — so data-gravity cost belongs in any multi-cloud decision, and cross-provider movement should be designed out rather than absorbed.
Since 2024, following EU regulatory pressure and a corresponding global policy change, AWS waives data-transfer-out fees for customers leaving AWS entirely and moving their data elsewhere. The waiver requires a request and covers full migration off AWS, not ongoing operational egress. It weakens the lock-in that egress fees created: the cost of leaving is now engineering effort, not a transfer penalty — and that belongs in any EDP negotiation as a stated alternative.
06 Cost-reduction framework
You cannot reduce what you cannot see, and the order of operations decides how much you save. Work these four steps in sequence — architectural reduction lowers the billable volume, then the contract discounts what remains.
Attribute before you act
Break the data-transfer line down by type in the Cost and Usage Report — internet, cross-region, cross-AZ, NAT processing, CloudFront. The split almost always surprises the team, and it produces the forecast a waiver is priced against.
Fix placement first
Co-locate data with the compute that consumes it in the same AZ to eliminate the charge, consolidate chatty cross-AZ services, and replace NAT gateways with VPC endpoints for AWS-service traffic to remove the $0.045/GB processing fee.
Route through the edge
Push customer-facing egress behind CloudFront to lower the blended rate, and standardize predictable data-center traffic on Direct Connect. Place the distribution tier in a low-egress US or EU region.
Commit the residual
Only now negotiate. Tie a committed-volume egress waiver to the clean forecast, add a CloudFront private pricing addendum, and fold a defined egress allowance into the EDP so a band of transfer is effectively free.
07 Negotiation levers
Egress waivers and discounts are negotiated inside the committed-spend agreement, not separately. The three contract levers below compound with the architecture fixes — each applies to a smaller billable volume once placement is corrected. See our committed spend discount guide for how egress sits inside the EDP.
A committed-volume egress discount tied to your forecast transfer. AWS prices it against a credible projection, so a clean attribution model is the precondition — not an afterthought.
A CloudFront private pricing addendum for high-volume distribution. Combined with routing egress behind the edge, it can cut the blended rate 30–50% before any account-level negotiation.
Inclusion of a defined egress allowance in the EDP so a band of transfer is effectively free. Fold it into the full agreement structure covered in the EDP pillar.
Stop overpaying for data transfer
Our Cloud & FinOps practice maps the spend, fixes the architecture, and negotiates committed-volume egress waivers — a median 41% cut.
The Licensing Edge
Weekly cloud and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.