Aws Data Transfer Pricing Calculator
AWS data transfer pricing is where cloud bills go to surprise people. The rates are tiered, they differ by route, and several of the most expensive routes never touch the public internet at all. This AWS data transfer pricing calculator prices each route the way AWS bills it: internet egress in volume tiers, CloudFront delivery with its own tiers plus request fees, inter-region and cross-AZ traffic, NAT Gateway processing and VPC peering, each as its own line with a printed tier breakdown.
The worked example used throughout is a mixed month: 500 GB of internet egress, 200 GB delivered through CloudFront with 2 million requests, 100 GB crossing regions, 200 GB crossing availability zones, and 100 GB each through a NAT Gateway and a VPC peering connection. It totals $46.50. For compute and storage pricing, use the whole-bill and EC2 calculators linked further down; this page prices movement only.
Rates are the documented list tiers the tool was verified against, last checked October 2026. AWS changes prices without notice and enterprise agreements discount them: confirm a budget that matters on the official AWS pricing pages.
Quick Answer
Key takeaways
- Data transfer into AWS is free; nearly every surprise is data moving out, across or between. The first 100 GB out to the internet each month is free, aggregated across all services and regions.
- Tiered means each gigabyte pays its own band's rate, not the top rate. 500 GB of egress costs $36.00, not the $45 a flat $0.09 multiplication suggests.
- CloudFront is the one route that can undercut direct egress: a 1 TB free band every month, cheaper tiers after it, and the origin-to-CloudFront hop itself is free.
- NAT Gateway processing at $0.045 per GB is the quiet multiplier in private-subnet designs. It charges for data that never leaves AWS.
- Quick Answer
- How to estimate a transfer bill route by route
- How the tier math works
- The two tier tables, in full
- Worked example: a $46.50 month of mixed traffic
- The internal charges people forget
- Three ways to cut the transfer bill
- What competing calculators miss
- Frequently asked questions
- Add This Calculator to Your Website
- References
How to estimate a transfer bill route by route
Start from your architecture, not your last invoice. List every path data travels in a month: out to the internet, through CloudFront if you front traffic with it, between regions for replication, between availability zones for chatty services, and through NAT Gateways or peering connections inside the VPC. Enter each volume in its own section and press Calculate. The result prices every route separately and prints the tier breakdown for egress and CloudFront, so you can see which band each gigabyte fell into rather than trusting a blended average.
Volumes are the hard part for most teams. CloudWatch and VPC flow logs report bytes per route; a week of real traffic scaled to a month beats a guess. If your question is the whole AWS bill rather than the movement inside it, price the stack in the aws cost calculator and bring the transfer total back here for tier detail.
How the tier math works
AWS prices egress like income tax brackets: each gigabyte pays the rate of the band it falls into, and only that band.
Classify the traffic. Every gigabyte belongs to exactly one route: internet egress, CloudFront delivery, inter-region, cross-AZ, NAT processing or peering. The route picks the rate table.
Apply the free allowance. Egress gets its first 100 GB free each month, aggregated across services. CloudFront delivery gets its first 1,024 GB in the free band of its own table.
Walk the bands. Fill each band at its own rate, then spill into the next: the free band first, then the full width of each paid tier (10 TB of egress at $0.09, the next 40 TB at $0.085, and so on), exactly the way AWS prices tier widths beyond the free allowance. 500 GB of egress fills the 100 GB free band, then prices 400 GB at $0.09.
Add the flat routes. Inter-region, cross-AZ, NAT and peering are single per-GB rates with no tiers, so they multiply straight through.
The two tier tables, in full
Internet egress from AWS services to the internet, per month, aggregated across the account:
| Monthly volume | Price per GB |
|---|---|
| First 100 GB | Free |
| Next 10 TB (after the free 100 GB) | $0.09 |
| Next 40 TB | $0.085 |
| Next 100 TB | $0.07 |
| All further volume | $0.05 |
CloudFront delivery in the US, Canada and Europe price classes this tool models:
| Monthly volume | Price per GB |
|---|---|
| First 1 TB | Free |
| Next 10 TB (after the free 1 TB) | $0.085 |
| Next 40 TB | $0.080 |
| Next 100 TB | $0.060 |
| Next 350 TB | $0.040 |
| Next 524 TB | $0.030 |
| Next 4 PB | $0.025 |
| All further volume | $0.020 |
These are the schedules published on the Amazon EC2 On-Demand pricing page for data transfer and the Amazon CloudFront pay-as-you-go pricing page. One note on requests: this tool deducts the Always Free allowance AWS publishes for CloudFront, the first 10 million requests per month, before pricing request fees, and the data tiers include the free 1 TB delivery band the same way.
Worked example: a $46.50 month of mixed traffic
The calculator is pre-filled with a small production footprint: a public site with a CDN in front, a replica in a second region, services spread across two availability zones, and private subnets reaching the internet through NAT.
| Route | Math | Monthly |
|---|---|---|
| Internet egress, 500 GB | 100 GB free + 400 x $0.09 | $36.00 |
| CloudFront data, 200 GB | inside the 1,024 GB free band | $0.00 |
| CloudFront requests, 2M at 90% HTTPS | inside the 10M free request allowance | $0.00 |
| Inter-region, 100 GB US to US | 100 x $0.02 | $2.00 |
| Cross-AZ, 200 GB | 200 x $0.01 | $2.00 |
| NAT Gateway, 100 GB processed | 100 x $0.045 | $4.50 |
| VPC peering, 100 GB | 100 x $0.01 x 2 sides | $2.00 |
| Total | $558.00 per year | $46.50 |
Scale changes the winner. At 10 TB of pure internet egress the same tier table returns $912.60 per month, which matches AWS's own published worked example for that volume. Push 2 TB through CloudFront with 10 million requests instead and the tool returns $87.04 for delivery plus $0.00 for requests, $87.04 in total: the free 1 TB band covers the first half of the delivery, the Always Free allowance covers every one of the 10 million requests, and the lower tiers do real work at volume.
The internal charges people forget
Three lines in the worked example never leave AWS, and together they cost more than the CloudFront bill. Cross-AZ traffic is billed at $0.01 per GB in each direction, so a round trip between services in different zones costs $0.02, and microservice chatter generates it invisibly: health checks, service meshes and replicated caches all count. NAT Gateway processing at $0.045 per GB is steeper per byte than first-tier internet egress after the free allowance math, and it applies to traffic from private subnets even when the destination is an AWS service that a gateway endpoint would have reached free. Peering is charged on both sides of the connection, which is why this tool doubles its $0.01 rate.
The compute generating this traffic has its own pricing traps, and the aws ec2 cost calculator covers the instance side, including why its simpler transfer line (first 100 GB free, then a flat rate) is a planning shortcut rather than the full tier schedule modeled here.
Three ways to cut the transfer bill
Front public content with CloudFront. The origin-to-CloudFront hop is free, delivery starts with a free terabyte, and every cached response is a response your origin never sends. At 10 TB a month, direct egress costs $912.60 while CloudFront delivery of the same volume costs $783.36 before request fees. Second, keep chatty services in one availability zone where the architecture allows it, and use gateway VPC endpoints for S3 and DynamoDB so private-subnet traffic stops paying NAT processing rates. Third, watch the inter-region line before adding replicas: at $0.09 per GB to Asia-Pacific, a chatty replication pattern can cost more than the second region's compute. Teams comparing clouds on transfer policy specifically should also run the whole stack through the azure cost calculator, because egress allowances are one of the few places the two providers still differ in structure, not just price.
What competing calculators miss
Most AWS calculators treat transfer as one flat rate times one volume, which gets 500 GB wrong by $9 and 10 TB wrong by hundreds. EgressCost runs a sharp single-purpose tool, but it prices S3 egress only: no CloudFront requests, no NAT, no cross-AZ, no peering. The detailed guides, Wring's transfer pricing map is the best of them, explain every route carefully and then leave the tier arithmetic to the reader. The official Pricing Calculator prices transfer correctly but buries it inside a full-estimate workflow built for whole architectures.
This page is the missing middle: all six transfer routes, real tier tables, a printed breakdown of which band each gigabyte fell into, and worked examples at three scales that reproduce against the published AWS figures.
Frequently asked questions
It depends on the band the gigabyte falls into. After a 100 GB monthly free allowance aggregated across services, internet egress costs $0.09 per GB for the first 10 TB beyond the free allowance, $0.085 for the next 40 TB, $0.07 for the next 100 TB and $0.05 above that, each rate applying only to the gigabytes inside its own band. So 500 GB costs $36.00, not $45.00, because the first 100 GB is free and only the remaining 400 GB pays the first paid rate.
Yes. Data transferred into AWS from the internet is not charged, across services and regions. The charges start when data moves out to the internet, between regions, between availability zones, or through services like NAT Gateway that bill per gigabyte processed.
AWS gives every account 100 GB of free data transfer out to the internet per month, aggregated across all services and regions rather than per service. In this calculator the egress tiers apply it automatically: the first 100 GB of the egress volume prices at $0. CloudFront delivery has a separate, larger free band of 1 TB per month in its own tier table.
Two charges stack. The gateway itself bills hourly for existing, and every gigabyte it processes costs $0.045, which is half the first paid egress rate, charged on traffic that may never leave AWS. Architectures that route all private-subnet traffic, including calls to S3 or DynamoDB, through NAT pay processing fees on everything. Gateway VPC endpoints for those services remove much of that traffic from the NAT path.
Yes. Traffic crossing between availability zones in the same region is billed at $0.01 per GB on the way out of one zone and again on the way into the other, so a request and its response each pay for their crossing. This calculator prices the volume you enter at $0.01 per GB; enter round-trip volume if you want the full both-directions figure for a chatty service pair.
For public content, usually yes. The transfer from your origin into CloudFront is free, the first 1 TB of delivery each month is in the free band, and the paid tiers start at $0.085 per GB against $0.09 for direct egress. At 10 TB a month this calculator prices direct egress at $912.60 and CloudFront delivery at $783.36 before request fees. Below the free bands the saving is mostly the request fees, and private or uncacheable traffic gains nothing.
Per 10,000 requests: $0.01 for HTTPS and $0.0075 for HTTP in the US, Canada and Europe price classes modeled here. This calculator blends the two by your HTTPS share, then multiplies by requests in units of 10,000. The first 10 million requests each month are free under the Always Free tier AWS publishes, and this calculator deducts them before pricing the rest. Two million requests at 90% HTTPS therefore cost $0.00 here, and 12 million requests would cost 200 x $0.00975 = $1.95, for the 2 million billable requests only.
No. The egress tiers and CloudFront prices here are the US and Europe schedules, which are the most common budgeting baseline. Asia-Pacific, South America and other regions run higher per-GB rates on several routes, and inter-region pricing depends on the specific pair, which is why the calculator offers route rates for the pairs it models and marks others for verification on the AWS pricing page.
Add This Calculator to Your Website
References
- Amazon Web Services, "Amazon EC2 On-Demand Pricing" - the data transfer out schedule: 100 GB free monthly aggregated, then $0.09, $0.085, $0.07 and $0.05 per GB tiers. AWS: EC2 Pricing and Data Transfer Tiers. Accessed October 2026.
- Amazon Web Services, "Amazon CloudFront Pricing: Pay As You Go" - delivery tiers by region and the per-10,000 HTTP and HTTPS request rates. AWS: CloudFront Pay As You Go Pricing. Accessed October 2026.
- Amazon Web Services, "Amazon CloudFront Pricing" - the Always Free tier of 1 TB of data transfer out and 10 million requests per month. AWS: CloudFront Pricing and Free Tier. Accessed October 2026.
- Amazon Web Services, "Amazon VPC Pricing" - NAT Gateway hourly and per-GB processing charges and VPC peering data rates. AWS: VPC and NAT Gateway Pricing. Accessed October 2026.
- Amazon Web Services, "AWS Free Tier" - the 100 GB data transfer out allowance aggregated across services and regions. AWS: Free Tier and Transfer Allowance. Accessed October 2026.
- Amazon Web Services, "AWS Pricing Calculator" - the official route for confirming transfer costs inside a complete architecture estimate. AWS Pricing Calculator. Accessed October 2026.