AWS Cross-Region Data Transfer Cost Calculator

Cross-region traffic (replication, multi-region reads, DR) can generate large bills. Use this calculator to estimate monthly cross-region transfer cost using your own $/GB assumptions.

Inputs

Cross-region transfer (GB / month)
Avg throughput: 9.14 Mbps.
Avg throughput (Mbps)
Est 24,624 GB/month.
Pricing mode
Use tiered mode when pricing changes by volume.
Cross-region price ($ / GB)
Enter your provider's effective $/GB for the region/path/tier.
Scenario presets

Results

Estimated monthly cost
$60.00
Egress
3,000 GB
Price
$0.02 / GB

How to get your inputs

  • GB/month: start from billing exports/flow logs; if you only have throughput, convert Mbps to GB/month.
  • Boundaries: separate cross-AZ vs cross-region vs internet egress as separate line items.
  • Effective rates: use your blended $/GB for the traffic mix you expect.

Result interpretation

  • Cross-region traffic is often one-way; confirm the billed direction.
  • Replication, DR, and backfill spikes should be modeled separately from steady-state.

Common mistakes

  • Mixing boundaries and applying the wrong $/GB rate.
  • Ignoring retries/timeouts that multiply traffic during incidents.

Input checklist

  • Identify source and destination region pairs.
  • Separate steady replication from one-time backfills or migrations.
  • Confirm billing direction (outbound vs inbound).

Advanced inputs to capture

  • Separate source and destination region pairs and track directionality.
  • Split steady replication traffic from one-time backfill or migration windows.
  • Distinguish cross-region transfer from cross-AZ and internet egress.
  • Adjust GB for compression or payload size changes where relevant.

Scenario planning

Scenario GB/month Direction Drivers
Baseline Expected Primary -> DR Steady replication
Peak High Primary -> DR Backfill/migration

Validate after changes

  • Validate the top transfer paths and AZ/region locality after architecture changes.
  • Re-check during peak windows (that's when hidden multipliers show up).

Next steps

Advertisement

Example scenario

  • If you replicate 3,000 GB/month across regions at $0.02/GB, estimated transfer cost is $60/month.

Included

  • Cross-region transfer estimate from GB/month and $/GB pricing.
  • Useful for replication, DR, and multi-region architectures.

Not included

  • Provider-specific free tiers, discounts, and tiered steps.
  • Replica storage costs (model separately).

How we calculate

  • Monthly cost = cross-region GB x price per GB.
  • Enter your provider's cross-region transfer price for the source/destination regions.
  • This page ignores free intra-zone traffic and tiering unless you reflect it in the inputs.

FAQ

Is cross-region transfer the same as internet egress?
No. Providers often price cross-region differently than public internet egress.
Does replication count both directions?
Typically replication traffic is billed on the outbound side. Confirm the billing direction for your service.

Related tools

Related guides

API Gateway vs ALB vs CloudFront cost: what to compare (requests, transfer, add-ons)
A practical cost comparison of API Gateway, Application Load Balancer (ALB), and CloudFront. Compare request pricing, data transfer, caching impact, WAF, logs, and the hidden line items that change the answer.
AWS cross-AZ data transfer cost: causes and estimate steps
A practical guide to AWS cross-AZ data transfer costs: common causes (load balancers, databases, Kubernetes), how to estimate GB crossing zones, and how to reduce it safely.
CloudFront cache hit rate: how it changes origin egress cost
Cache hit rate strongly influences origin requests and origin egress (cache fill). Learn a simple model, what breaks hit rate, and the practical levers to improve it safely.
CloudFront pricing: estimate bandwidth and request costs (without hardcoding prices)
A practical way to estimate CloudFront-style CDN costs using your own bandwidth ($/GB) and request-fee ($ per 10k/1M) assumptions, plus common pitfalls like tiered pricing and origin egress.
Lambda vs Fargate cost: a practical comparison (unit economics)
Compare Lambda vs Fargate cost with unit economics: cost per 1M requests (Lambda) versus average running tasks (Fargate), plus the non-compute line items that often dominate (logs, load balancers, transfer).
AWS network cost guide: NAT, VPC endpoints, PrivateLink, and data transfer (what to model)
A practical AWS network cost hub: how to model NAT Gateway, VPC endpoints/PrivateLink, and cross-AZ/cross-region data transfer. Includes formulas, break-even workflow, and a troubleshooting checklist.
Advertisement

Disclaimer

Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.

Last updated: 2026-02-07