AWS data transfer costs are notoriously opaque. While compute and storage costs are relatively straightforward to forecast and optimise, data transfer charges accumulate silently across dozens of service interactions — inter-AZ traffic, cross-region replication, API Gateway responses, CloudFront origin fetches, NAT Gateway processing — often amounting to 10–20% of a large AWS bill with little visibility until the invoice arrives.
This article is part of our AWS Enterprise Negotiation Guide. For a broader treatment of cloud egress costs across AWS, Azure, and GCP, see our cloud egress costs guide. For the commercial negotiation angle — including what AWS will and won't discount on data transfer — this article covers the full picture.
AWS charges for data leaving its network (egress to internet) and for data moving between Availability Zones within the same region. Inter-AZ transfer at $0.01/GB in each direction adds up rapidly for distributed architectures. Organisations that properly map and optimise their inter-AZ traffic patterns frequently uncover $100K–$500K+ in annual avoidable charges.
Understanding AWS Data Transfer Pricing
AWS data transfer pricing has three distinct categories, each with different cost dynamics and optimisation levers. Understanding the category structure is the prerequisite for any meaningful cost reduction programme.
Category 1: Internet Egress (Data Out to Internet)
Data transferred from AWS services to the public internet incurs per-GB charges that decrease with volume. This is the most widely discussed data transfer cost and applies to EC2, S3, CloudFront origin-to-edge, and many managed services.
| Monthly Volume | Price per GB (us-east-1) | Notes |
|---|---|---|
| First 10 TB | $0.09/GB | Standard tier |
| Next 40 TB (10–50 TB) | $0.085/GB | Small volume discount |
| Next 100 TB (50–150 TB) | $0.07/GB | Mid-volume |
| Above 150 TB | $0.05/GB | High-volume tier |
| Via CloudFront | $0.0085–$0.12/GB (region-dependent) | Lower than EC2 direct for most regions |
Category 2: Inter-Region Transfer
Data transferred between AWS regions incurs charges in both directions for most services. Inter-region transfer rates range from $0.02/GB to $0.09/GB depending on the region pair. This is a significant cost driver for organisations with multi-region architectures, disaster recovery replication, or data aggregation pipelines that consolidate data from regional deployments to a central region.
Category 3: Inter-AZ Transfer
Data transferred between Availability Zones within the same region is charged at $0.01/GB in each direction — effectively $0.02/GB round trip. This appears modest but is the most underestimated data transfer cost for organisations running distributed application tiers, microservice meshes, or Kubernetes clusters across multiple AZs.
Free Data Transfer Scenarios
It is equally important to understand what AWS does not charge for. Data transferred into AWS from the internet (ingress) is free. Data transferred between services within the same Availability Zone using private IP addresses is free. Data transferred from EC2 to S3 within the same region is free (when using the S3 VPC endpoint). Understanding these free paths enables architectural decisions that avoid unnecessary charges.
Top Data Transfer Cost Drivers in Enterprise Environments
1. Distributed Application Tiers Across AZs
Three-tier architectures (web, application, database) deployed across three AZs for high availability generate inter-AZ traffic at every tier boundary. A medium-traffic application processing 10 TB of inter-tier traffic per month incurs approximately $200/month in inter-AZ charges — not dramatic individually, but multiplied across dozens of applications in a large estate, this compounds to meaningful six-figure annual spend.
2. Cross-AZ Kubernetes Pod Communication
Kubernetes clusters spanning multiple AZs generate inter-AZ traffic for every cross-AZ pod-to-pod communication. Without topology-aware routing, a busy microservice mesh can generate tens of terabytes of inter-AZ traffic monthly. See our Kubernetes cost optimisation guide for topology-aware routing configuration strategies.
3. NAT Gateway Processing
NAT Gateways are charged both for hourly presence ($0.045/hour per AZ) and for data processed ($0.045/GB). Organisations with multiple NAT Gateways across AZs, combined with heavy outbound internet traffic from private subnets, frequently find NAT Gateway as their second- or third-largest data transfer line item. S3 and DynamoDB traffic should always route through VPC Gateway Endpoints (free) rather than NAT Gateways.
4. CloudFront Origin Fetches
CloudFront origin requests to S3 or EC2 origin servers incur data transfer charges at the origin tier. While CloudFront-to-internet delivery is cheaper than EC2-to-internet delivery, organisations with low cache hit rates can still accumulate significant origin fetch costs. Optimising CloudFront cache behaviours to increase hit rates reduces both origin fetch costs and origin infrastructure load.
5. Cross-Region Data Replication
S3 Cross-Region Replication, RDS cross-region read replicas, and DynamoDB Global Tables all incur inter-region transfer charges on top of the replication storage costs. For data-intensive workloads, replication transfer can be a major cost driver that is easy to overlook in architecture reviews.
Data Transfer Pricing by Service: Key Reference Table
| Transfer Type | Approx. Price | Direction | Optimisation Approach |
|---|---|---|---|
| EC2 to internet | $0.09/GB (first 10 TB) | Outbound | Use CloudFront; compress responses |
| CloudFront to internet | $0.0085–$0.012/GB (US) | Outbound | Improve cache hit rate; use compression |
| Inter-AZ (same region) | $0.01/GB each way | Both | AZ-affinity routing; topology-aware k8s |
| Inter-region | $0.02–$0.09/GB | Both | Minimise cross-region calls; use local caches |
| NAT Gateway processing | $0.045/GB | Processed | VPC endpoints for S3/DynamoDB; Gateway LB |
| VPC Peering (same region) | $0.01/GB each way | Both | Same as inter-AZ; use Transit Gateway if complex |
| S3 → EC2 (same AZ) | Free | Inbound | Ensure same AZ for data-intensive workloads |
| S3 → EC2 (different AZ) | $0.01/GB | Inbound to EC2 | Use S3 VPC endpoint; co-locate with data |
What Can You Negotiate on Data Transfer?
AWS data transfer pricing is generally not directly negotiable as a standalone line item in the same way that compute or storage discounts are. However, there are several mechanisms through which enterprise buyers can reduce effective data transfer costs through commercial negotiation.
EDP Discount Application
Your AWS Enterprise Discount Program (EDP) discount applies to eligible AWS services — and data transfer charges on many services are EDP-eligible. This means that a 15% EDP discount reduces your effective data transfer cost by 15% automatically. See our AWS EDP negotiation playbook for how to maximise your EDP discount level.
Custom Data Transfer Pricing for Very High Volumes
Organisations with very high data transfer volumes — typically $500K+ per year in data transfer charges — can sometimes negotiate custom data transfer pricing through private pricing negotiations. This is not a standard offering, but AWS account teams have discretion to bring custom pricing proposals to their approval chain for customers where data transfer represents a competitive concern or where the customer is evaluating CDN or cloud alternatives.
CloudFront Volume Pricing
CloudFront has a published volume discount tier structure, but AWS also offers custom CloudFront pricing for high-volume customers through its CloudFront Private Pricing programme. If CloudFront delivery is a significant part of your AWS bill, engage your account team about private CloudFront pricing — particularly if you can credibly present a comparison with Cloudflare or Fastly alternatives.
AWS Direct Connect Pricing
For organisations with substantial data transfer between on-premises environments and AWS, AWS Direct Connect typically delivers lower data transfer rates than internet egress pricing ($0.02/GB outbound on Direct Connect vs $0.09/GB standard internet egress). Direct Connect also provides predictable bandwidth without the burstability cost of internet transfer. If your data transfer profile includes significant on-premises-to-AWS or AWS-to-on-premises movement, Direct Connect should be evaluated as a cost reduction mechanism, not just a connectivity solution.
12 Strategies to Reduce AWS Data Transfer Costs
Building a Data Transfer Cost Governance Programme
One-time optimisation exercises are valuable but insufficient on their own. Data transfer costs grow with application scale and architectural changes. Building sustainable governance means establishing data transfer as a tracked metric in your FinOps practice.
Start by creating a baseline report in AWS Cost Explorer that shows data transfer costs segmented by transfer type (internet egress, inter-region, inter-AZ) and by account or application tag. Set anomaly detection alerts for unexpected spikes in data transfer spend. Establish a monthly review cadence where data transfer costs are reviewed alongside compute and storage costs in your cloud cost governance process.
For a complete framework for cloud cost governance including data transfer, see our cloud cost governance policies guide. For how data transfer costs interact with your overall AWS commercial arrangements, our FinOps enterprise guide provides the operating model context.
Concerned About Hidden AWS Data Transfer Costs?
Our specialist advisory partners can identify and quantify your data transfer cost reduction opportunities as part of an AWS commercial review engagement.
Request a Review →Frequently Asked Questions
Is data transfer into AWS free?
Yes. Data transferred into AWS from the internet (ingress) is free. AWS charges for data leaving its network (egress) and for inter-AZ and inter-region transfers within AWS.
Are inter-AZ data transfer charges included in the EDP discount?
EDP discounts apply to most AWS services, and inter-AZ data transfer charges on services like EC2 are typically EDP-eligible. Confirm with your account team which specific data transfer line items are covered under your EDP terms.
Can I negotiate custom data transfer rates with AWS?
Direct negotiation of data transfer unit pricing is possible for customers with very high data transfer volumes (typically $500K+/year in transfer charges). This requires a business case and is handled through AWS's private pricing process. More commonly, EDP discounts and CloudFront private pricing are the accessible commercial levers.
What is the cheapest way to deliver content to end users from AWS?
Using Amazon CloudFront is typically the cheapest path for internet content delivery from AWS — CloudFront rates are approximately $0.0085/GB in US regions vs $0.09/GB for direct EC2 egress. For very high volumes, custom CloudFront pricing may be available.