AWS VPC Data Transfer Cost Calculator
This calculator is the bill-conversion page of the VPC transfer cluster: use it after the transfer boundary, monthly GB, and effective path-specific rate are believable enough to translate into spend. It is intentionally a calculator, not a traffic-forensics workflow.
Maintained by CloudCostKit Editorial Team. Last updated: 2026-07-22. 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.
Inputs
Results
- Validate the transfer boundary and effective rate before changing architecture assumptions.
- Capture one baseline and one peak month to avoid hidden spike surprises.
Model VPC transfer by boundary, not by one blended rate
This calculator becomes useful only after you identify the actual boundary you are paying for. Cross-AZ, cross-region, and internet-facing paths may all move bytes from the same application, but they are not the same billing event. The biggest mistake is collapsing them into one average number too early.
The built-in Mbps helper is only a quick throughput-to-GB convenience, not a defendable path-measurement workflow. Use the VPC transfer guide or cross-AZ diagnosis guide when the path, AZ locality, or billing usage type still needs evidence.
- 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.
Calculator role in this cluster
- This page owns: known-boundary GB x effective rate bill conversion.
- The VPC transfer guide owns: classifying whether the bytes crossed AZ, region, NAT, endpoint, or internet boundaries.
- The cross-AZ guide owns: AZ-locality diagnosis before you decide the cross-AZ share.
- The egress calculator owns: baseline-vs-peak planning for outbound or external transfer once that boundary is known.
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
Example scenario
- If you validated 2,000 GB/month of cross-AZ service traffic and have the effective $/GB for that path, convert it into monthly transfer spend.
- If a topology change moved traffic across a region or AZ boundary, model the recurring baseline separately from the migration or failover peak.
Included
- Bill conversion from monthly GB and a path-specific $/GB assumption.
- One VPC transfer boundary per run: cross-AZ, cross-region, or another already-classified VPC path.
- Mbps-to-GB helper for quick throughput conversion when monitoring gives only average bandwidth.
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.
- Defendable path measurement, flow-log attribution, or boundary classification.
How we calculate
- Monthly transfer cost = GB/month x $/GB.
- Model one known VPC transfer boundary at a time, then sum rows outside the calculator.
- If you have free allowances, subtract them before applying rates.
FAQ
What should I use for GB/month?
Why are transfer bills surprising?
How do I avoid underestimating cross-AZ transfer?
Related tools
Related guides
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-07-22. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .