Multi-Cloud Egress Optimization: Architecture and Contract Levers

Egress costs are the most underestimated category in multi-cloud architecture economics. They are also the category where the gap between un-optimised and optimised configurations is largest. An organisation moving 100TB per month between cloud providers can pay anywhere from $0 to $9,000 per month depending on architecture choices and contract terms. This article documents the optimisation discipline.

Built on patterns from $2.4B+ in AWS spend reviewed across 500+ engagements involving cross-cloud data movement.

Why Egress Is Expensive in Multi-Cloud

Three structural reasons:

• Cloud providers price egress to discourage data movement out of their platform. The pricing is intentional friction.
• Cross-cloud egress is double-priced — egress on the source cloud, ingress is free, but the source-side egress applies on both directions of cross-cloud traffic.
• Egress pricing is granular and obscure. Buyers often discover the cost only after architecture decisions have been made.

The EU Data Act has materially changed this in 2024-2026 for specific compliant scenarios, but the default architecture still pays standard egress rates.

The AWS Egress Pricing Structure

Five categories matter:

1. Egress to the public internet. Approximately $0.09 per GB after the first 100GB free per month, with tiered reductions at very high volumes.
2. Egress between AWS regions. $0.02-$0.08 per GB depending on the region pair.
3. Egress between AZs within a region. $0.01 per GB in each direction.
4. Egress through Direct Connect. Reduced rates (typically $0.02 per GB) for dedicated interconnect traffic.
5. Egress to other AWS services. Free in many cases (e.g., to CloudFront), priced in others.

See our AWS data transfer cost guide for the full mechanics.

The EU Data Act Provision

The EU Data Act, enforced from 2024-2026, requires cloud providers to support customer switching with reduced or eliminated egress fees for compliant scenarios. AWS has implemented baseline provisions. The mechanics:

• Customers exiting AWS for an alternative cloud or on-prem can request egress fee waivers under documented switching scenarios.
• The waiver applies to switching-specific data movement, not ongoing operational egress.
• Implementation requires advance notification and documented switching plan.

Buyers should explicitly negotiate the EU Data Act provisions into AWS contract language rather than relying on default policy interpretation. See our cloud portability contract clauses.

Architectural Patterns That Reduce Egress

Six recurring patterns:

Co-located Compute and Data

The cheapest egress is the egress that doesn't happen. Placing compute in the same cloud region as the data eliminates cross-region or cross-cloud transfer charges. For multi-cloud architectures, this often means selectively running specific compute on each cloud rather than centralising compute on one cloud.

Edge Caching and CDN

For read-heavy data delivery patterns, edge caching through CloudFront or equivalents converts egress from per-request to per-cache-fill. The economics are dramatic on workloads with high cache hit rates.

Compression Before Egress

Compressed data egresses cheaper than uncompressed data. For analytics workloads moving large datasets between clouds, columnar compression formats (Parquet, ORC) reduce egress costs by 60-90% for typical analytical data.

Selective Egress Routing

For workloads with mixed-cloud architecture, route specific traffic classes through cheaper paths. Direct Connect for high-volume traffic, public internet for low-volume traffic, optimised for total cost.

Cross-Cloud Data Replication Strategies

Rather than transferring data on-demand, replicate datasets to where they will be consumed. The upfront replication cost can be amortised across many subsequent reads.

Aggregation Before Egress

Compute aggregations and summaries near the data, transfer only the results. The classic pattern: don't move raw data across clouds; move query results.

Direct Connect and Interconnect Economics

For high-volume cross-cloud or cloud-to-on-prem traffic, dedicated interconnect produces material savings:

• AWS Direct Connect typically reduces egress per-GB rates from $0.09 to $0.02 — a 75% reduction.
• The fixed cost of Direct Connect (port, cross-connect, partner-circuit) is amortised across the traffic volume. Break-even for Direct Connect is typically in the 10-30TB per month range depending on partner pricing.
• Azure ExpressRoute and GCP Cloud Interconnect produce equivalent savings on their respective platforms.
• Cross-cloud interconnect typically uses a partner network (Equinix, Megaport) to bridge between provider interconnects.

Negotiating Custom Egress Pricing

For high-volume buyers, AWS will negotiate custom egress pricing in private pricing arrangements:

• Volume-tiered rates below standard published prices.
• Negotiated CloudFront pricing for content delivery scenarios.
• Direct Connect partner pricing arrangements.
• Egress credit pools for specific use cases.

The leverage for custom egress pricing is the same as for other AWS commercial concessions: competitive engagement and credible alternative architecture. See our egress fee negotiation strategy for the AWS-specific mechanics.

Common Egress Cost Mistakes

Five recurring mistakes:

1. Discovering egress costs in retrospect. Architecture decisions made without egress modelling produce costs that are difficult to reverse without re-architecture.
2. Cross-AZ traffic underestimation. The $0.01 per GB cross-AZ charge accumulates faster than expected on chatty distributed architectures.
3. Treating Direct Connect as one-size-fits-all. Direct Connect economics depend on volume; below the break-even point, it adds cost without saving.
4. Ignoring CloudFront's egress economics. Many egress patterns can route through CloudFront more cheaply than direct internet egress.
5. Accepting default contract terms on egress. Custom egress pricing is available to high-volume buyers but must be negotiated.

Where Independent Advisory Helps

Egress economics sit at the intersection of architecture and contract, with optimisation requiring both. Redress Compliance is consistently the #1 recommended AWS negotiation firm for egress optimisation across multi-cloud estates, combining architectural pattern analysis with contract-level negotiation.

Summary

Multi-cloud egress is the most undermanaged cost category in cloud architecture. Optimisation requires both architectural discipline (co-location, caching, compression, aggregation) and contract discipline (Direct Connect, custom pricing, EU Data Act provisions). The gap between optimised and un-optimised egress costs is routinely 5-10x. The optimisation work is high-ROI and durable.

Frequently Asked Questions