Cross-Region Transfer Minimization

Inter-region data transfer is the second-largest data transfer line item on the typical enterprise AWS bill, after Internet egress. At $0.02/GB for most region pairs (higher for São Paulo, Cape Town, Bahrain, Hong Kong, and other distant pairs), inter-region transfer accumulates fast on cross-region replication, multi-region database architectures, DR snapshot copies, and content distribution networks not fronted by CloudFront.

This guide details how cross-region transfer accumulates, where the biggest cost concentrations sit, and the architectural and contractual moves that consistently reduce cross-region spend by 30-55 percent in our $2.4B+ AWS spend review portfolio.

How inter-region transfer bills

Source region	Destination region	Rate / GB
US-East-1 (Virginia)	US-West-2 (Oregon)	$0.02
US-East-1	EU-West-1 (Ireland)	$0.02
US-East-1	AP-Southeast-2 (Sydney)	$0.02
Most pairs	Most pairs	$0.02
Any region	South America — São Paulo	$0.080-0.138
Any region	Middle East — Bahrain / UAE	$0.110-0.138
Any region	Africa — Cape Town	$0.110-0.147
Any region	Asia Pacific — Hong Kong	$0.090-0.110

Two facts:

1. Egress from source is billed; ingress to destination is free. Don't double-count.
2. Distant pairs cost 5-7x more than mainstream pairs. Architectures that span São Paulo or Cape Town inherit a disproportionate share of bill.

Where inter-region transfer hides

The big six cost concentrations:

1. S3 Cross-Region Replication (CRR)

Every replicated object incurs the egress fee. CRR is also paid in destination storage and source-side request fees, but the egress dominates at any meaningful volume. A 50 TB/month CRR rule from US-East to EU-West bills $1,000/month in transfer alone.

Common waste patterns:

• CRR rules replicating ephemeral or test data that doesn't need DR coverage.
• CRR rules replicating to a storage class that defeats the purpose (e.g. Standard destination when Glacier Deep Archive preserves RPO).
• Stale CRR rules that survived bucket lifecycle changes.

See S3 lifecycle policies for the destination-side optimization that often pairs with CRR cleanup.

2. Multi-region database replication

Aurora Global Database, DynamoDB Global Tables, and RDS cross-region read replicas all incur inter-region transfer at $0.02/GB on replication traffic. For write-heavy applications with global footprints, this category can dominate.

3. Cross-region EBS snapshot copies

DLM and AWS Backup cross-region copy policies incur the standard inter-region transfer rate on the underlying data. Daily snapshot copies on multi-TB volumes generate large bills.

4. Cross-region container image pulls

ECR cross-region image pulls bill at $0.02/GB. Large containers (>1 GB) pulled by hundreds of nodes across regions can rack up significant fees.

5. Misplaced compute

Compute in region A reading from S3 or RDS in region B incurs the full inter-region fee on every read. This is almost always architectural debt.

6. CloudFront edges and origin replication

CloudFront edge locations are global, but origin pulls hit the configured origin region. If your origin is US-East and a viewer in Singapore hits a cold edge, the resulting origin pull is intra-AWS but not free.

Minimization strategies

Strategy 1: Audit and prune CRR rules

The single highest-leverage move on cross-region transfer optimization is auditing every CRR rule. Across our engagements, the average enterprise has 42 percent of its CRR-replicated bytes in rules that no longer serve a DR or compliance purpose. Prune ruthlessly. For data that genuinely needs DR coverage, redirect to Glacier-class destinations — the transfer fee is the same but destination storage drops 80-95 percent.

Strategy 2: Consolidate replication paths

Many enterprises replicate the same content multiple times because different teams set up separate CRR rules. One consolidated replication path can deliver the same DR coverage at one-third the inter-region transfer cost.

Strategy 3: Snapshot copy frequency

Daily cross-region snapshot copies are rarely justified by RPO. Most production workloads can move to weekly cross-region copies with daily intra-region copies, dropping inter-region transfer by 85 percent on the snapshot category.

Strategy 4: Container registry replication

ECR cross-region replication (the service feature) bills the same inter-region transfer fee, but only replicates the manifest and layers once. Per-node pulls then hit the local region. Enabling ECR cross-region replication and reconfiguring node configs to pull from local region cuts the per-pull inter-region cost to zero.

Strategy 5: Compute and data co-location

Identify any compute reading data from another region. If the read pattern is sustained, co-locating the compute or the data eliminates the inter-region cost entirely. Most pipelines have at least one such hidden pattern.

Strategy 6: CloudFront fronting

For public S3 reads or ALB-fronted dynamic content with global viewership, CloudFront eliminates many cross-region calls implicitly — viewers hit the local edge, and origin pulls are free. See CloudFront vs direct transfer for the decision framework.

The contract levers

Cross-region transfer fees are highly negotiable on EDPs above ~$500K annual data transfer. Specific levers:

• CRR egress waivers: For DR-mandated buckets, AWS will waive cross-region replication egress as part of EDP commitments. We have negotiated $400K+ in annualized waiver value on a single agreement.
• Aurora Global / DynamoDB Global Table credits: For multi-region database architectures, AWS will credit the inter-region replication transfer fees.
• Cross-region snapshot copy credits: For compliance-driven DR copies, AWS will credit the inter-region transfer line.
• Distant-region surcharge negotiation: For São Paulo, Cape Town, and Middle East regions, the elevated rates are negotiable on committed volume.

Case study: $620K cross-region baseline

A global financial services firm we engaged with had $620K annual inter-region transfer. Composition: 43% CRR, 28% Aurora Global Database, 14% cross-region snapshots, 8% ECR pulls, 7% misplaced compute reads.

The intervention:

• CRR audit: pruned 31 rules covering ephemeral and obsolete data. Reduced CRR volume by 38%.
• Redirected remaining CRR to Glacier-class destinations on 14 buckets. Preserved DR posture, dropped destination storage 80%.
• Reduced cross-region snapshot copy frequency from daily to weekly. Reduced snapshot inter-region transfer by 85%.
• Configured ECR cross-region replication. Eliminated per-pod cross-region pulls.
• Negotiated 60% credit on Aurora Global Database replication egress in EDP renewal.
• Negotiated waiver of CRR egress on three DR-mandated buckets.

Net result: cross-region spend dropped from $620K to $192K annualized — a 69 percent reduction. Architecture contributed roughly 40% and contract negotiation 60% of the total savings.

Action checklist

1. Pull 90 days of Cost & Usage Reports filtered to inter-region transfer line items. Segment by source and destination region.
2. Audit every S3 CRR rule. Prune unused; redirect remaining to Glacier-class destinations.
3. Review cross-region snapshot copy frequency. Move from daily to weekly where RPO permits.
4. Enable ECR cross-region replication for any cluster pulling images across regions.
5. Identify any compute reading data from another region. Co-locate where sustained.
6. Scope CRR waivers and Aurora/DynamoDB Global credits into your next EDP renewal.
7. Contact our advisory team for a cross-region transfer audit benchmarked against $2.4B+ of reviewed AWS spend.

Cross-region transfer is one of the most under-optimized categories on enterprise AWS bills, and one of the most negotiable on EDP renewals. The combination of architectural pruning, replication-frequency rationalization, and contract-side credit negotiation routinely delivers 40-70 percent reductions. See our complete data transfer cost guide for how cross-region fits the broader transfer-cost picture.

Frequently asked questions