AWS VPC Data Transfer Cost Calculator

Data transfer is often the hardest cloud line item to predict. This AWS VPC data transfer cost calculator helps you estimate monthly spend from GB/month and your $/GB assumptions. Use it for cross-zone, cross-region, and internet egress style modeling.

Inputs

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

Results

Estimated monthly cost
$40.00
Egress
2,000 GB
Price
$0.02 / GB

How to get your inputs

  • GB/month: start from billing exports or flow logs; if you only have throughput charts, convert Mbps to GB/month using Units converter.
  • $ / GB: use your effective rate for the specific boundary (cross-AZ, cross-region, internet).

Result interpretation

  • Boundary mix is the primary driver; split cross-AZ, cross-region, and internet.
  • Small % increases in east-west traffic can outweigh compute savings.

Common mistakes

  • Mixing boundaries (cross-AZ vs cross-region vs internet) and using the wrong $/GB rate.
  • Ignoring cache fill / origin egress (CDN) that shifts cost to another place.
  • Under-modeling retries/timeouts that multiply traffic during incidents.

Scenario planning

Scenario Boundary GB/month Drivers
Baseline Cross-AZ Expected Normal traffic
Peak Cross-region High Failover/migration

Validate after changes

  • Validate top transfer paths and their boundaries (cross-AZ vs cross-region vs internet).
  • Re-check after routing or AZ locality changes; small shifts can create big costs.
  • Compare measured GB/month to billing usage types and adjust assumptions.

Next steps

AWS network cost hub Cross-AZ transfer cost VPC data transfer guide
Advertisement

Example scenario

  • If you move 2,000 GB/month across boundaries at your $/GB -> estimate monthly transfer spend.
  • Transfer costs can exceed compute for chatty microservices or data-heavy pipelines.

Included

  • Transfer cost estimate from GB/month and $/GB pricing assumptions.
  • Useful for internet egress, cross-boundary transfers, and general transfer modeling.

Not included

  • Per-hour gateway fees (e.g., NAT gateway hourly) and per-connection pricing.
  • Provider-specific exceptions and free allowances unless you model them separately.

How we calculate

  • Monthly transfer cost = GB/month x $/GB.
  • If you have multiple transfer types (internet egress, cross-region, cross-zone), model each separately and sum.
  • If you have free allowances, subtract them before applying rates.

FAQ

What should I use for GB/month?
Start from monitoring/flow logs/billing exports. If you only have average throughput, convert Mbps to GB/month with the Units Converter.
Why are transfer bills surprising?
Because many architectures have hidden east-west traffic. Cross-zone service calls, replication, and cache fill can create large GB/month totals.
How do I avoid underestimating cross-AZ transfer?
Segment by architecture: load balancer paths, service-to-service calls, and replication. Validate AZ locality (client and backend in the same AZ) and model a peak scenario.

Related tools

Data egress cost (generic) NAT gateway cost Load balancer cost Cross-region transfer cost Units converter AWS network cost hub Guide: VPC data transfer Guide: cross-AZ transfer cost

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 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.
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 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.
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