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.

Maintained by CloudCostKit Editorial Team. Last updated: 2026-02-07. Editorial policy and methodology.

Best next steps

Use this calculator for the first estimate, then validate the answer with the closest guide or companion tool.

Data egress cost (generic) NAT gateway cost Load balancer cost Cross-region transfer cost

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

Model VPC transfer by boundary, not by one blended rate

This calculator becomes useful only when you identify the actual boundary you are paying for. Cross-AZ, cross-region, and internet paths may all move the same bytes, but they are not the same commercial event. The biggest mistake is collapsing them into one average number too early.

  • Cross-AZ: east-west traffic created by placement or load-balancing choices.
  • Cross-region: replication, DR, and geographically split architectures.
  • Internet egress: public delivery, partner traffic, or downloads leaving the platform.

Why transfer grows before anyone notices

Transfer cost often rises without a corresponding jump in user traffic because topology changes are enough to create new billable boundaries. A service moved to another AZ, a cache miss path, or a new replication stream can create meaningful spend long before application owners realize the path changed.

  • Chatty services: many small east-west calls can outweigh compute gains.
  • Failover or balancing changes: a resilience decision can silently create new cross-AZ traffic.
  • Cache and origin behavior: a CDN miss or cache refill can move cost, not eliminate it.
  • Retry amplification: incident windows can multiply transfer without lasting traffic growth.

Boundary-first checklist before you trust the number

  • Map the top transfer paths and label each as cross-AZ, cross-region, or internet before assigning rates.
  • Keep CDN origin traffic, replication, and service-to-service traffic as separate lines even if they share similar units.
  • Use measured monthly GB where possible, and convert throughput carefully only when metrics are all you have.
  • Do not treat a blended rate as final unless you know the boundary mix is stable.

Baseline vs topology-shift transfer scenarios

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

How to review transfer after an architecture change

  • Validate the top transfer paths and confirm the billed boundary still matches your intended design.
  • Re-check after routing, failover, cache, or AZ-locality changes because small topology shifts can create large costs.
  • Compare measured GB/month to billing usage types before assuming optimization efforts actually saved money.

Next steps

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

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.
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.
AWS Network and Data Transfer Cost Guide
A practical AWS network cost hub for data transfer, NAT Gateway, VPC endpoints, PrivateLink, and cross-AZ or cross-region pricing. Built to support AWS data transfer calculator and network-cost workflows.

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. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .