AWS data transfer is not one universal egress fee. The charge depends on the service, source and destination, Region, Availability Zone, direction, and network path—so the first step is to identify the billed usage type and resource before changing the architecture.
Why AWS data transfer charges are easy to misread
AWS names outbound data transfer as one of its three fundamental cost drivers, alongside compute and storage: “There are three fundamental drivers of cost with AWS: compute, storage, and outbound data transfer.” But “data transfer” on a bill is a family of charges, not a single rate. Internet egress, traffic between Availability Zones (AZs), traffic between Regions, and service-specific flows can be billed differently.
As an Amazon Associate I earn from qualifying purchases.
The same application may generate multiple chargeable segments. A request might pass through a load balancer, NAT Gateway, Transit Gateway, or another intermediary before reaching its destination. A CDN can add its own delivery charges while changing the origin path. The bill category alone may not show which resource or route caused the cost.
Free tools Windows power users keep installed
One-click scans. No signup required.
How to identify the resource and path behind a charge
- Start in Cost Explorer. Filter for transfer-related usage categories and look for service-specific entries such as EC2 inter-AZ transfer, S3 internet transfer, or region-to-region transfer. AWS describes these categories in its Cost Explorer documentation.
- Use detailed billing data for attribution. In a Cost and Usage Report (CUR) or AWS Data Exports, inspect the product code, usage type, Region indicators, and resource identifiers when available. Product code can help distinguish CloudFront data transfer from internet egress. AWS explains the relevant billing fields in its CUR data dictionary.
- Group the results. Break transfer costs down by service, AWS Region, transfer type, and resource. AWS’s CUDOS dashboard analysis uses these dimensions in its data-transfer and networking views, including examples involving NAT Gateway, Transit Gateway, EC2, S3, and CloudFront.
- Trace the actual network route. Follow the traffic through its internet gateway or NAT, load balancer, VPC endpoint, peering connection, Transit Gateway, AZ or Region boundary, and CDN or origin. A single workload can cross several potentially chargeable segments.
- Check current rates for the exact path. Use AWS’s current service and regional pricing pages once you know the source, destination, direction, and usage type. A generic egress estimate will not reliably represent a service-specific route.
What the main transfer paths mean
Internet traffic
AWS’s architecture guidance describes inbound transfer as uncharged across services and Regions, while outbound internet transfer is charged by service, with rates tied to the originating Region. That explanation is from a 2021 AWS Architecture Blog article; treat it as a model of the pricing distinctions, not a substitute for current service terms and rates.
#1 Best Overall
Inter-AZ and inter-Region traffic
Traffic between AZs and Regions has distinct billing categories. To find it, look for the corresponding usage types in Cost Explorer or detailed billing data, then match the transfer to the communicating resources and their locations. The relevant charge depends on the service and path, not just the fact that data left one resource.
S3 and CloudFront
For S3, AWS’s support article describes a 100 GB-per-month internet-egress allowance aggregated across AWS services and Regions, with China and GovCloud (US) excluded, and lists specific transfer exceptions. Because allowances and exceptions can change, verify the current AWS guidance on identifying S3 data transfer costs and the terms applicable to your account before using that figure in a forecast.
CloudFront delivery and transfer from an origin to CloudFront are separate things to examine. CloudFront usage reports record bytes served from edge locations; any applicable S3-to-CloudFront transfer charges appear under AWS Data Transfer. Compare the origin path with viewer delivery rather than assuming the CDN makes egress free or necessarily cheaper. AWS documents the billing distinction in its CloudFront usage report guide.
NAT Gateway and Transit Gateway
Intermediaries can add costs beyond the transfer category that first drew attention. AWS’s CUDOS analysis highlights NAT Gateway, Transit Gateway, and inter-AZ costs as items to investigate. Transit Gateway can also incur per-GB data-processing charges when traffic traverses it. Check both the route and each relevant service’s current pricing; do not attribute every networking charge to internet egress.
How to decide whether an architecture change will save money
Use the identified route and billed usage type to compare alternatives. Consider all of the following together:
- Transfer path and direction: Which billed usage type changes, and how much data moves along that segment?
- Service, Region, and AZ: Where do the source and destination run, and does the proposed change alter their locations?
- Intermediary processing: Does traffic still pass through NAT Gateway or Transit Gateway, and what processing or other service charges apply?
- Other architecture costs: Include requests, endpoint or delivery charges, redundancy, and any new service costs—not just the transfer line.
- Operational requirements: Evaluate latency, availability, failover, and reliability alongside the bill.
Investigate cross-AZ traffic without weakening resilience
If communicating services send large volumes across AZs, check why. Keeping them in the same AZ may reduce some transfer, but distributing services across AZs can support availability and failover. The right choice depends on the workload’s resilience requirements and the full cost of the design.
Check whether a VPC endpoint changes the route
AWS’s architecture guidance says same-Region S3 or DynamoDB traffic can use VPC gateway endpoints to avoid data transfer charges for that communication. Confirm that the endpoint applies to the traffic you are tracing and assess any other service costs in the actual design before treating it as a saving.
Compare content delivery paths end to end
For content delivery, compare origin transfer, CloudFront delivery, request charges, caching behavior, and direct access to the origin. The viewer-facing delivery charge and the origin-to-edge path are not interchangeable billing questions; examine both in the usage data.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What your bill can—and cannot—tell you
Cost Explorer and detailed billing records can identify categories and, where the data includes it, the relevant resource. They do not by themselves establish which architecture is best or what a redesign will save. AWS’s published examples show useful analysis dimensions, not a general savings percentage or a representative share of an AWS bill. For a reliable comparison, connect the billed usage to the real network route, then price the complete alternatives using current service and regional rates.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
