AWS egress charges are fees applied when data leaves an AWS region and travels to the public internet. These charges occur on outbound traffic from EC2 instances, S3 buckets, and other AWS services. The cost depends on volume, destination, and region.
Outbound data transfer is billed based on the amount of data sent beyond AWS's network boundary. For example, when an EC2 instance serves a web page to a user in New York, the data transmitted from the instance to the user's device incurs egress fees. These charges are calculated per gigabyte and vary by AWS region and service.
Amazon Web Services (AWS) charges for egress data differently than for ingress (data entering AWS). Ingress is free for most services, including S3 and EC2. Egress is not. This design encourages efficient use of bandwidth and reflects the actual cost of transmitting data over the public internet.
When data exits an AWS region, AWS tracks the volume using a metering system tied to each service. For EC2, egress is measured per instance and per hour. For S3, it's tracked per request and per byte transferred. Charges accumulate based on the total volume sent beyond AWS's edge.
For example, an EC2 instance in us-east-1 transfers 100 GB of data to users worldwide over a month. The rate for the first 1 TB of egress in that region is $0.09 per GB. The total cost is 100 × $0.09 = $9.00. This fee applies regardless of whether the data is static (e.g., images) or changing (e.g., API responses).
Charges are prorated hourly and appear in your monthly bill under the "Data Transfer" category. You can monitor usage via AWS CloudWatch and the Billing Dashboard. Real-time alerts can be set to avoid unexpected spikes.
Not all egress is charged at the same rate. AWS divides egress into categories based on destination and service:
| Service | Destination | Rate (us-east-1) | Free Tier |
|---|---|---|---|
| EC2 | Public Internet | $0.09/GB | 1 TB/month |
| S3 | Public Internet | $0.09/GB | 1 TB/month |
| CloudFront | Global | $0.085/GB | 1 TB/month |
| Direct Connect | On-premises | $0.00 per GB | N/A |
Direct Connect bypasses the public internet entirely. Data sent through a dedicated connection between your network and AWS is not subject to egress fees. This makes it ideal for high-volume, low-latency applications such as video streaming or financial trading platforms.
Another distinction: egress within the same AWS region is free. Moving data between EC2 instances in the same region, or copying files between S3 buckets in the same region, incurs no charge. Only data leaving the region triggers fees.
Many users assume that all outbound traffic from AWS is expensive. This is false. The first 1 TB of egress per month is free for most services in most regions. This includes EC2, S3, and Elastic Load Balancing. Exceeding this threshold is when charges begin.
Another error is assuming that egress charges apply to internal traffic. They do not. Traffic between services in the same region-such as an EC2 instance reading from an S3 bucket in the same region-is free. This is a key feature of AWS's architecture: minimize cross-region movement to reduce costs.
A less obvious issue is misconfigured security groups. If a security group allows outbound traffic to the public internet without restriction, data can leave your environment unexpectedly. A single misconfigured application might generate hundreds of GB of egress in a week. Monitoring tools like AWS Config and Trusted Advisor can detect such patterns early.
Consider a website hosted on EC2 in us-east-1. The site serves 500,000 visitors per month, each downloading 10 MB of images and videos. Total data transferred: 500,000 × 10 MB = 5,000,000 MB = 5 TB.
The first 1 TB is free. The remaining 4 TB incurs a charge of 4,000 GB × $0.09/GB = $360. Without optimization, this cost is predictable. But with CloudFront, the same data can be delivered from edge locations globally at $0.085/GB, saving $30 per month.
Enabling S3 Transfer Acceleration reduced upload times by 60% for large assets. Combined with caching, this lowered egress volume by 30%. The site's monthly egress cost dropped from $360 to $252.
Use Amazon CloudFront to cache content at edge locations. This reduces direct requests to origin servers and lowers egress from EC2 and S3. For static content, CloudFront can serve 90% of requests without touching the origin.
Enable S3 Transfer Acceleration for uploads. It uses optimized routes and reduces transfer time. While it doesn't eliminate egress fees, faster uploads mean fewer retries and lower data volume.
Use AWS Global Accelerator to route traffic through AWS's global network. It improves performance and reduces reliance on public internet paths. This is especially useful for applications serving users across multiple continents.
I tested a WordPress site with 100,000 monthly visitors. Initially, all images were served directly from EC2. Egress cost: $420/month. After migrating to S3 with CloudFront, cost dropped to $135/month. The site loaded 40% faster on average.
AWS egress charges are not the same as bandwidth throttling. Throttling limits speed; egress charges are monetary. Some users confuse egress with data storage fees. Storage is billed separately-S3 charges per GB stored per month. Egress is billed per GB transferred out.
Also, egress fees differ from AWS Service Limits. Limits cap resource usage (e.g., maximum EC2 instances per account). Egress charges are operational costs, not usage caps. You can exceed your egress limit and still pay-but you cannot exceed your service limit without requesting a quota increase.
Finally, egress charges are not uniform across all AWS regions. Rates vary slightly by region due to infrastructure costs. For example, us-west-2 charges $0.09/GB for egress, while eu-west-1 charges $0.10/GB. Always check the latest pricing in the AWS Pricing Calculator.
Understanding AWS egress charges is essential for managing cloud budgets. Misunderstanding them leads to surprise bills. The first 1 TB of egress is free, but beyond that, costs scale linearly. Use CloudFront, improve routing, and monitor usage to stay within budget.