Why Egress Is the Most Underestimated Cloud Cost
Cloud egress — charges for data leaving a cloud provider's infrastructure — is the cost that enterprises most frequently underestimate, most rarely negotiate, and most consistently overpay. It's rarely the largest line item on a cloud bill, but it's often the most inefficient: the place where default settings and procurement blind spots combine to leave significant money on the table.
This article is part of our Cloud Pricing Benchmarks: AWS vs Azure vs GCP Complete Guide. Here we focus specifically on the full egress pricing picture — internet egress, inter-region data transfer, multi-cloud data flows, and the negotiation strategies that reduce these costs by 30-50%.
Based on analysis of 180 enterprise cloud contracts, the average enterprise is overpaying on egress by $340,000 annually. The distribution is skewed: organizations with large datasets, high-throughput applications, or multi-cloud architectures face egress costs that can reach $2-5M annually — with 40-60% of that theoretically negotiable or avoidable.
The Egress Blind Spot
In 73% of enterprises we benchmark, cloud egress costs are not included in commitment negotiations with AWS, Azure, or GCP. This means organizations renew compute and storage commitments at negotiated rates while continuing to pay list price on data transfer — often one of their fastest-growing cloud cost categories.
How Cloud Egress Pricing Is Structured
Cloud data transfer costs exist across multiple categories. Understanding the structure is the prerequisite to optimizing it.
The Four Types of Cloud Data Transfer Costs
- Internet egress: Data transferred from cloud to the public internet (to end users, external APIs, CDN origins). The most common and often the most expensive category.
- Inter-region transfer: Data moved between geographic regions within the same provider. Often forgotten in architecture design; can be substantial for globally distributed applications.
- Inter-availability zone (AZ) transfer: Data moved between availability zones within the same region. AWS and Azure charge for this; GCP does not (within the same region). This distinction has meaningful architectural implications.
- Cross-provider transfer: Data moved from one cloud provider to another (AWS to Azure, for example). Charged as egress at the source and sometimes as ingress or processing at the destination.
Importantly: ingress (data flowing into a cloud provider) is generally free from all three major providers. The cost asymmetry — free in, charged out — creates a structural vendor lock-in mechanism that cloud providers are unlikely to change.
Egress Rate Benchmarks: List Price and Negotiated
Internet Egress Rates: AWS, Azure, and GCP Compared
| Monthly Volume | AWS (S3/EC2 to Internet) | Azure (to Internet) | GCP (to Internet) |
|---|---|---|---|
| First 100 GB | Free | Free (first 5GB, then $0.087) | Free |
| 1 TB/month | $0.09/GB ($92/TB) | $0.087/GB ($89/TB) | $0.08/GB ($82/TB) |
| 10 TB/month | $0.085/GB (tiered) | $0.083/GB (tiered) | $0.06/GB (tiered) |
| 150+ TB/month | $0.07/GB | $0.05/GB | $0.06/GB |
| Enterprise negotiated (annual $5M+ spend) | $0.04–$0.06/GB | $0.03–$0.05/GB | $0.03–$0.05/GB |
At 100TB/month of internet egress, the difference between AWS list rate ($0.085/GB) and enterprise negotiated rate ($0.05/GB) is $3,600 per month — $43,200 annually — for a single egress cost category. Scale that to organizations transferring 500TB-1PB monthly, and the gap is $200K-$500K/year from egress negotiation alone.
Inter-Region Transfer: The Architecture Tax
| Transfer Type | AWS | Azure | GCP |
|---|---|---|---|
| Within same region, same AZ | Free | Free | Free |
| Within same region, different AZ | $0.01/GB (both directions) | $0.01/GB | Free (within same region) |
| US regions to US regions | $0.02/GB | $0.02/GB | $0.01/GB |
| US to EU or APAC | $0.02–$0.08/GB | $0.02–$0.08/GB | $0.01–$0.06/GB |
The GCP inter-AZ free transfer advantage is significant for high-throughput applications. Applications with active-active deployments across multiple availability zones (a common high-availability pattern) incur $0.02/GB on AWS ($0.01 each direction) but $0 on GCP. For an application moving 200TB/month between AZs, this represents $4,000/month or $48,000/year in pure architecture-driven cost difference.
Multi-Cloud Egress: The Most Expensive Data Flow
Data transferred between cloud providers — AWS to Azure, GCP to AWS, etc. — is charged at full egress rates at the source. There is no discount for multi-cloud transfer; all three providers treat cross-provider traffic identically to internet egress.
| Multi-Cloud Flow | Monthly Volume | Annual Cost (List Rate) | Annual Cost (Negotiated) |
|---|---|---|---|
| AWS → Azure (data sync) | 10 TB/month | $10,200 | $6,000–$7,200 |
| AWS → Azure (data sync) | 100 TB/month | $96,000 | $48,000–$60,000 |
| AWS → GCP (ML pipeline) | 50 TB/month | $48,000 | $24,000–$30,000 |
| Multi-cloud backup (all 3) | 200 TB/month total | $204,000 | $96,000–$120,000 |
Benchmark Your Egress Costs
We identify where your cloud egress costs exceed market benchmarks and quantify the negotiation opportunity — typically 30-50% reduction available.
Negotiating Egress Pricing: What's Actually Achievable
Cloud providers will negotiate egress pricing for enterprises with sufficient volume. Here's what's achievable and how to approach it.
AWS Egress Negotiation
AWS includes egress discounts in EDP (Enterprise Discount Program) negotiations for customers spending $5M+ annually. The mechanism is typically an egress credit pool rather than a rate reduction — AWS applies a credit to offset data transfer charges each month up to a negotiated cap.
Benchmark outcome: enterprises that explicitly quantify egress volume in EDP negotiations receive egress credits averaging 35-50% of their annual egress spend. The critical step is quantification — if you don't bring a number to the table, AWS will treat egress as a non-issue.
Additionally, AWS Direct Connect (dedicated network connections from on-premises to AWS) has negotiated pricing for high-volume customers that's 40-60% below standard rates. If your architecture involves regular large data transfers between on-premises and AWS, Direct Connect economics may be compelling.
Azure Egress Negotiation
Azure is generally more flexible on egress negotiation than AWS, particularly in the context of EA renewals. Microsoft's account teams can authorize egress discounts of 30-50% for enterprise customers with documented high-volume transfer needs.
Azure ExpressRoute (dedicated connectivity) follows a similar negotiation pattern to AWS Direct Connect. Enterprise pricing for ExpressRoute is commonly 35-55% below list for $3M+ Azure spend customers.
GCP Egress Negotiation
GCP's egress pricing is already the most competitive at list rates among the three providers, but Enterprise Agreement negotiations can reduce internet egress costs by an additional 25-40% for high-volume customers.
GCP also offers Cloud Interconnect (dedicated connectivity) with negotiated pricing for customers committing to specific throughput levels. One specific GCP advantage: for organizations with workloads running on GCP that serve users primarily in regions where GCP has significant infrastructure (North America, Western Europe), GCP's CDN integration with Cloud CDN can offset origin egress costs substantially.
Architectural Strategies to Reduce Egress Costs
Negotiation reduces egress costs. Architecture eliminates them. The most effective egress optimization combines both approaches.
01 — CDN-First Architecture
Moving static content to CDN reduces origin pull egress substantially. AWS CloudFront, Azure CDN, and GCP Cloud CDN all have negotiated pricing available, and their per-GB rates are significantly lower than origin egress for equivalent volumes. An enterprise serving 5PB/month to internet users through CDN vs. direct S3 origin typically saves 45-60% on those data transfer costs.
02 — Optimize Multi-Cloud Data Flows
The most expensive egress is often multi-cloud synchronization that could be redesigned. Questions to evaluate:
- Does that data actually need to exist in both clouds simultaneously, or could it live in one with on-demand replication?
- Could a shared storage layer (Snowflake, Delta Lake, etc.) replace the data movement entirely?
- Is the multi-cloud architecture driven by business requirements or historical accident?
03 — Compression Before Transfer
Trivial but consistently underimplemented: compressing data before cross-region or internet transfer reduces egress costs proportionally. For text-heavy data formats (JSON, CSV, logs), compression ratios of 5:1 to 10:1 are achievable, reducing effective egress costs by 80-90% for those data types.
04 — Consolidate Regional Footprint
Organizations that reduced from 4 active regions to 2 primary regions (with passive DR in a third) as part of a FinOps initiative saved an average of $280,000 annually in inter-region transfer costs in our sample — without meaningful impact on application performance or resilience.
Egress Cost Reduction Analysis
We identify your top 3 egress cost reduction opportunities — architectural and contractual — with quantified impact estimates.
Conclusion: Include Egress in Every Cloud Negotiation
The core message of this benchmarking report is straightforward: egress is negotiable, egress costs are frequently above market rates, and the two-step solution (negotiate the rate, then optimize the architecture) consistently produces meaningful savings.
Your action checklist:
- Pull your cloud bills and isolate egress costs by category. Internet egress, inter-region, and cross-provider flows should each be quantified separately.
- Compare your effective egress rates to the benchmarks above. If you're paying list rates, you're almost certainly above market.
- Include egress in your next cloud renewal negotiation. Bring the volume number. Ask specifically for egress credits or rate reductions as part of your EDP/EA/CUD negotiation.
- Evaluate your multi-cloud data flows. Some are necessary. Many are remnants of architecture decisions that could be redesigned for lower cost.
- Consider CDN coverage. If you're not using CDN for static and semi-static content delivery, start there — it's the highest-ROI single change for egress-heavy organizations.
For enterprises spending $5M+ on cloud, egress optimization typically represents a $200,000-$1,500,000 annual opportunity. Our benchmark analysis will show you exactly where you stand.