Cloud Exit and Reversibility on AWS (2026): Egress, Portability, and the Contract Clauses Procurement Actually Asks For

As of May 2026, the cost of leaving AWS has been quietly redefined—twice. First, the EU Data Act (Regulation (EU) 2023/2854) made its cloud-switching obligations applicable on 12 September 2025, and requires switching and data-egress charges to fall to zero by 12 January 2027 (Article 29). Second, AWS already waives data-transfer-out-to-internet charges for customers moving off AWS (request credits through AWS Support).

So if egress is free, why do exits still stall? Because the egress bill was never the expensive part. This article is for CTOs, enterprise architects, and procurement leads who get asked “what’s our exit strategy?” and need a defensible answer that isn’t “we’d go multi-cloud.” It pairs a reversibility scorecard with an exit cost model—and argues for AWS-first with funded exit ramps, not multi-cloud theater.

Benchmark pattern (not a cited client) — A composite mid-market SaaS estate (~50 TB stored, Aurora + a DynamoDB-backed feature, ~40 Lambda functions, Cognito auth) modeled for full exit: list-price egress ~$4,403, $0 after the AWS leaving-AWS waiver, but ~$113k of engineering re-platform time (database and serverless logic dominate). Numbers come from the exit cost model—plug in your own rates and volumes.

The cost of leaving is not the egress line

The instinct is to estimate exit cost as data volume × egress rate. That number is now close to irrelevant:

Opinionated take: Stop modeling exit as an egress problem and start modeling it as a re-platform problem. The egress waiver and the Data Act removed the line item everyone quotes; what remains is the engineering time to unwind proprietary managed services. That is the number that belongs in your commit negotiation.

Reversibility is per-workload, not per-estate

You don’t make “AWS” reversible. You make specific workloads reversible, and you pay the premium only where it buys leverage. Score each anchor workload with the reversibility scorecard:

Pick stickiness deliberately. DynamoDB and Lambda are good engineering for the right workload—the mistake is choosing them by reflex and discovering the lock-in during a price change.

What broke — During a reversibility drill for a logistics-style workload, the team had clean Terraform and Postgres on RDS, scoring as “reversible.” The restore-elsewhere test still failed on day two: a single Lambda held the only copy of an order-state machine encoded as EventBridge rules, with no portable definition. Detected when the parallel environment couldn’t replay events. Fix: extracted the state machine into a portable Step Functions-Local-compatible definition checked into the repo. Lesson—the scorecard lies if you never run the drill.

What procurement actually wants in the contract

When an enterprise buyer asks for an exit clause, three concrete things satisfy them—and the EU Data Act gives you a ready-made template even outside the EU:

1. Data-return format — machine-readable, documented schema export, not “we’ll give you a tarball.”
2. Exit-assistance window — a defined period and scope of vendor help during migration.
3. Notice + porting period — the Data Act mandates a 30-day porting window and a max two-month notice for in-scope EU customers. Mirror it.

Note what the Act does not prohibit: proportionate early-termination penalties on committed-spend agreements. Reversibility lowers your re-platform cost; it does not erase a multi-year EDP shortfall. Model both.

AWS-first with exit ramps beats multi-cloud-by-default

Reversibility tempts teams toward standing multi-cloud “so we’re never locked in.” That trades a hypothetical exit cost for a guaranteed daily operational tax: doubled tooling, doubled on-call surface, lowest-common-denominator architecture. For most mid-market estates, AWS-first with a funded, time-boxed exit ramp per anchor workload is the better trade. We make that case in detail in the multi-cloud vs AWS-first decision guide.

What to do this week

1. List your 3 anchor workloads (the ones tied to your commit or regulated portability clauses).
2. Run the reversibility scorecard on each. Record the score.
3. For any workload scoring ≤8, write down the re-platform project cost—that number is your switching cost, and your negotiation lever.
4. Add data-return format, exit-assistance window, and notice/porting period to your MSA template before the next renewal.

Reproduce this — Clone the exit cost model CSV and the reversibility scorecard. Replace the illustrative engineer-week rates and data volume with yours. Verify the egress waiver path in the AWS blog post and confirm DTO list rates on the AWS pricing page for your source Region.

What this post doesn’t cover

• Full data-center exit / large-scale migration program mechanics (a separate program-management topic).
• Multi-region resilience cost trade-offs (without doubling costs).
• Data residency / sovereignty obligations (2026 sovereignty guide).
• Legal interpretation of the EU Data Act—pair this with counsel; we are not a law firm.
• Detailed NAT/data-transfer cost tuning while you stay (NAT gateway billing, data-transfer costs).

Related: Cloud migration consulting · AWS managed services · FinOps on AWS

If you only do one thing: Run a restore-elsewhere drill on your single most important workload this quarter. A reversibility claim you have never tested is a liability, not an asset.