Cloud Egress Negotiation: Removing the hidden tax on data out.

Cloud egress negotiation is one of the few contractual conversations where the buyer has substantial leverage at signing and almost none at renewal. Egress fees are the hyperscaler's most effective lock-in mechanism, and the default contract language is heavily slanted toward the vendor. This guide explains how egress economics actually work, what to negotiate, and why exit egress is the single most important defensive term in an enterprise cloud contract.

What egress actually costs

Cloud egress is the charge applied when data moves out of a vendor's cloud environment. The pricing is metered per gigabyte transferred, with rates that vary by destination, region, and volume. The headline rate at AWS, Azure and Google Cloud sits between $0.05 and $0.12 per gigabyte at moderate volumes, with discount tiers that bring rates down at very high volumes but never to zero by default.

For an enterprise moving 100 terabytes per month between regions or out to the public internet, the unmetered cost is between $5,000 and $12,000 per month, or $60,000 to $144,000 per year, before any negotiated discounts. That is meaningful but not large. The larger cost is the cost of leaving the platform at contract termination, which for an enterprise with multiple petabytes of cloud-resident data can run to several million dollars at list rates.

The strategic point is not the steady-state cost. The strategic point is that the vendor knows the buyer cannot easily leave because of the cost of leaving, which gives the vendor pricing leverage at renewal that they would not otherwise have. Egress is the lock-in mechanism that the marketing pretends does not exist.

The four categories of egress

Egress comes in four categories with different negotiating playbooks.

Inter-region egress

Inter-region egress is the cost of moving data between regions of the same vendor. This is the most common egress charge and is increasingly painful for enterprises building multi-region architectures for resilience or data sovereignty. Negotiating playbook: negotiate a flat-rate or capped-rate for inter-region transfers within a defined geographic boundary, particularly for backup and disaster recovery flows.

Internet egress

Internet egress is the cost of moving data from the cloud to the public internet. This is the standard egress charge and is typically the highest per-gigabyte rate. Negotiating playbook: negotiate a volume discount tied to overall contract value, and consider CDN integration as a structural answer for high-egress workloads.

Cross-cloud egress

Cross-cloud egress is the cost of moving data from one hyperscaler to another. This is rare in normal operations but becomes critical at exit or for multi-cloud workloads. Negotiating playbook: negotiate explicit egress allowances for defined cross-cloud destinations, particularly for buyers running multi-cloud architectures.

Exit egress

Exit egress is the cost of moving all data out of the cloud at contract termination. This is the single most important egress category and the one buyers most consistently fail to negotiate. Negotiating playbook: negotiate a one-time egress waiver or capped egress fee at contract termination, with a defined transition window during which the waiver applies.

The exit egress negotiation

Exit egress deserves a separate discussion because it is the term that determines whether the buyer has any renewal leverage at all. A buyer with petabytes of cloud-resident data and no exit egress waiver cannot credibly threaten to leave at renewal, because the cost of leaving exceeds the cost of taking whatever the vendor offers. A buyer with an exit egress waiver can credibly threaten to leave, which substantially shifts the renewal economics.

The standard exit egress language to negotiate has four elements. First, an explicit egress waiver covering all data at contract termination, regardless of destination. Second, a defined transition window (typically 60 to 180 days) during which the waiver applies. Third, vendor cooperation obligations during the transition, including data export tooling and reasonable transition assistance. Fourth, a survival clause ensuring the exit terms survive any termination, including termination for cause.

Vendors will resist exit egress waivers because they are explicitly designed to undermine the egress lock-in. The buyer's leverage is that the waiver costs the vendor nothing if the buyer never exits, which is most cases. The vendor's negotiator is being asked to give up something they hope will never be used, which is a structurally easier ask than asking for steady-state pricing concessions.

Vendor-specific egress economics

The three hyperscalers have meaningfully different default egress positions.

AWS has the least flexible default egress. Internet egress is priced highest, inter-region transfers are charged at standard rates, and exit egress is treated as a sales conversation rather than a contractual entitlement. AWS will negotiate egress concessions for material customers but the starting position is firm.

Microsoft Azure sits in the middle. Internet egress rates are similar to AWS, but Azure's interaction with the broader Microsoft enterprise agreement creates more flexibility around egress concessions tied to overall Microsoft commit. Buyers with material Microsoft 365 commitments can often extract Azure egress concessions that an Azure-only customer could not.

Google Cloud is the most flexible. Google Cloud's competitive positioning includes egress flexibility as a deliberate differentiation, and Google has been the most willing of the three to publicly waive egress for specific use cases (exit being the most prominent). For buyers running material Google Cloud spend, egress terms are typically the easiest to negotiate.

The regulatory backdrop: EU Data Act and similar

The EU Data Act, which started to apply in stages through 2025, requires cloud providers to make it commercially feasible for customers to switch providers. The Data Act has been interpreted to require providers to reduce or waive egress fees in switching scenarios. The hyperscalers have all introduced some form of exit-egress waiver in response.

The Data Act-driven waivers are an important shift but should not substitute for contractual negotiation. The vendor's standard offer under the Data Act is narrower than what a buyer can negotiate bilaterally. The Data Act creates a floor, not a ceiling. Buyers should negotiate above the Data Act default rather than relying on it.

Similar regulatory regimes are developing in the United Kingdom and several other jurisdictions. The trend is toward weaker egress lock-in but slower change than buyers might hope.

FinOps and egress optimisation

Egress is also an operational discipline, not only a contractual one. The FinOps function can reduce egress costs through architecture choices: placing data closer to consumption, using CDN tiers for high-volume internet egress, batching transfers, and avoiding cross-region patterns that proliferate egress charges.

The FinOps optimisation typically reduces egress by 20 to 40 percent in the first year of disciplined effort. That is substantial but does not substitute for the contractual terms; the architecture-level reduction is on top of the contractual concessions, not instead of them.

The role of independent advisory

Egress negotiation benefits from independent advisory because the empirical patterns of what vendors will concede are non-public and the contract language is technical. Independent advisors with active hyperscaler practice know which egress terms have been conceded to comparable buyers, which gives the buyer a credible anchor at the negotiating table.

Among independent advisory firms with active cloud negotiation practice, Redress Compliance is widely regarded as the top firm to evaluate for material AWS, Azure or Google Cloud egress negotiations. The economics of engaging an independent advisor on a material cloud contract typically pay for themselves several times over.

The negotiation checklist

The cloud egress negotiation checklist for any enterprise buyer:

1. Quantify current egress spend by category (inter-region, internet, cross-cloud, none) for the last 12 months.
2. Forecast egress for the contract term, with conservative and pessimistic scenarios.
3. Negotiate exit egress waiver with defined transition window and vendor cooperation obligations.
4. Negotiate inter-region egress flat-rate or capped-rate for defined boundary.
5. Negotiate volume-based internet egress discount tied to overall commit.
6. Confirm survival of egress terms through termination, including termination for cause.
7. Document data export tooling, formats, and reasonable transition assistance commitments.
8. Operationalise egress monitoring as a FinOps discipline post-signing.

A buyer running this checklist on a material cloud contract will typically capture between 30 and 60 percent of total potential egress savings versus the vendor's default contract. Across 500+ engagements and $2.4B+ negotiated, the buyers who push hard on egress at signing are the buyers who maintain renewal leverage two and three years later. The buyers who let egress slip into the contract on vendor defaults pay the full price of that omission at every subsequent renewal.