The hidden cloud egress costs nobody flags
Your actual egress cost can run well above the headline rate: in the worked example below, 64 percent more. NAT Gateway processing, cross-AZ transfer, API Gateway charges, load balancer fees, VPC endpoint costs, all silently multiply your bill. Use the calculator for base rates, then read this page to understand the real total.
Worked example, us-east-1, 50 TB a month (51,200 GB, as AWS counts its tiers). Internet egress: 10,240 GB at $0.09 ($921.60) plus 40,960 GB at $0.085 ($3,481.60) = $4,403.20. Add NAT Gateway processing on every byte (51,200 GB x $0.045 = $2,304), three zonal NAT Gateways running all month (3 x $0.045 x 730 hours = $98.55), ALB capacity units with processed bytes as the billing dimension (51,200 GB x $0.008 = $409.60) and one ALB's hourly charge ($16.43): $7,231.78. Cross-AZ hops and API Gateway would add more. Arithmetic is ours, over the published AWS rates on this page.
The Six Hidden Egress Costs
These are the charges that cloud providers document but do not prominently advertise. Each one is legitimate and avoidable with the right architecture decisions.
NAT Gateway Processing
$0.045/GB+ $0.045/hrHigh ImpactEvery byte flowing through a NAT Gateway incurs a $0.045/GB processing charge, on top of the standard internet egress rate. This is separate from and additional to the egress fee itself. A NAT Gateway running 24/7 also costs $32.85/month in hourly charges. At 10TB/month, the processing fee alone is $450, often exceeding the base egress cost. If your NAT Gateway is in a different AZ from your workload, add another $0.01/GB for cross-AZ transfer.
Enable VPC Gateway Endpoints for S3 and DynamoDB (free). Use Interface Endpoints for other AWS services. Consider IPv6 for internet-facing workloads. Regional NAT Gateway (Nov 2025) simplifies multi-AZ NAT and can avoid cross-AZ charges, but bills per active AZ so it does not reduce the hourly cost.
Cross-AZ Data Transfer
$0.01/GB each way($0.02/GB round trip)High ImpactData moving between Availability Zones costs $0.01/GB in each direction, totalling $0.02/GB for a request-response round trip. With a standard 3-AZ architecture, roughly two-thirds of internal service-to-service communication crosses AZ boundaries. A microservices architecture with 10TB/month of internal traffic generates $100-200/month in cross-AZ charges. Load-balanced traffic automatically distributes across AZs, making this unavoidable for HA deployments.
Co-locate tightly coupled services in the same AZ. Use connection-aware load balancing (prefer same-AZ). Cache frequently accessed data locally. Consider AZ-aware routing for read-heavy workloads.
API Gateway Data Transfer
$0.09/GB(on top of per-request fees)Medium ImpactAPI Gateway charges standard internet egress rates for data transfer out, on top of its per-request pricing ($1.00-3.50 per million requests). This is often overlooked because it appears as a separate line item from your EC2/Lambda egress in the bill. For APIs returning large payloads (file downloads, data exports, paginated lists), the data transfer charges can exceed the request charges. A REST API serving 10TB/month pays $900 in data transfer alone.
Compress API responses with gzip/brotli. Paginate large responses. Use CloudFront in front of API Gateway (caches GET requests, reduces origin egress). Consider direct ALB for non-REST workloads.
Load Balancer Data Processing
$0.008 per LCU-hour (ALB)+ $0.0225/hr per ALBMedium ImpactApplication Load Balancers bill $0.008 per Load Balancer Capacity Unit (LCU) hour and Network Load Balancers $0.006 per NLCU-hour (us-east-1). Each hour is billed on whichever dimension is highest: new connections, active connections, rule evaluations or bytes processed. One ALB LCU covers 1 GB processed per hour for EC2 targets, so for byte-heavy traffic the charge works out at about $0.008/GB: an ALB processing 10,000 GB a month, spread evenly, pays about $80 in LCU charges, plus $16.43/month in hourly charges ($0.0225 x 730 hours). The flat $0.008 per GB processed meter belongs to the Classic Load Balancer. These charges apply to all traffic through the load balancer, not just internet-bound traffic.
There is no way to avoid load balancer processing fees if you need load balancing. Optimize by reducing payload sizes, enabling compression, and consolidating load balancers where possible. For internal services, consider service mesh or direct service discovery.
VPC Interface Endpoints
$0.01/GB + ~$0.01/hrper AZMedium ImpactInterface VPC Endpoints (for services like SQS, SNS, KMS, CloudWatch, ECR, etc.) charge both per-GB and per-hour fees. The hourly charge is $0.01 per hour per AZ in us-east-1, which is $7.30/month per AZ over a 730-hour month. In a 3-AZ setup, that is $21.90/month just for the endpoint to exist, before any data transfer. The per-GB charge of $0.01 applies to the first 1 PB processed each month. However, Interface Endpoints can still save money by avoiding NAT Gateway processing fees ($0.045/GB).
Always use Gateway Endpoints for S3 and DynamoDB (free, no per-GB or hourly charges). For other services, an Interface Endpoint saves $0.035/GB against a NAT Gateway ($0.045 less $0.01), so it pays for its hourly charge at about 209 GB/month per AZ it runs in ($7.30 / $0.035), about 626 GB/month for a 3-AZ endpoint ($21.90 / $0.035).
Cross-Region Replication
$0.01-$0.02/GB(varies by region pair)High ImpactMulti-region disaster recovery architectures incur cross-region transfer costs on all replicated data. S3 Cross-Region Replication, RDS read replicas, DynamoDB Global Tables, and Aurora Global Database all generate inter-region transfer charges: from us-east-1 that is $0.01/GB to us-east-2 (Ohio) and $0.02/GB to us-west-2 or to Ireland, Frankfurt and London. A DR setup replicating 10,000 GB a month from us-east-1 to an EU region costs about $200/month in transfer fees, or $100 to us-east-2. These costs double if you replicate to more than one secondary region.
Evaluate whether cross-region replication is truly required for your recovery objectives. Consider replicating only critical data rather than entire datasets. Use S3 Intelligent-Tiering to reduce storage before replication. For read replicas, consider whether a warm standby in a single region meets your RTO requirements.
Hidden Cost Audit Checklist
Run through this 10-point checklist against your own cloud architecture to identify hidden egress costs. Each item can save hundreds or thousands of dollars per month.
Related Resources
Related Guides
Frequently Asked Questions
Is egress free within the same region on AWS?
It depends. Traffic within the same Availability Zone using private IP addresses is free. However, cross-AZ traffic costs $0.01/GB in each direction ($0.02/GB round trip), even within the same region. Since most production architectures use multiple AZs for high availability, this internal traffic adds up quickly. None of it shows up in the headline internet egress rate.
What is cross-AZ data transfer cost on AWS?
Cross-AZ data transfer on AWS costs $0.01 per GB in each direction, totalling $0.02/GB for a round trip. This applies to all traffic between Availability Zones, including inter-service communication, database replication, and load-balanced traffic. With a typical 3-AZ architecture, approximately two-thirds of your internal traffic crosses AZ boundaries. This is one of the most commonly overlooked costs: a service processing 10TB/month internally can generate $100-200/month in cross-AZ charges alone.
How much does NAT Gateway cost on AWS?
AWS NAT Gateway charges $0.045 per GB for data processing plus $0.045 per hour for each gateway (approximately $32.85/month just for running). If your traffic also crosses AZ boundaries to reach the NAT Gateway, add another $0.01/GB. At 10TB/month through NAT Gateway, processing fees alone are $450/month, before any internet egress charges. For a detailed analysis and alternatives, see our dedicated NAT Gateway cost guide.
What are VPC endpoint costs?
VPC endpoints come in two types with very different pricing. Gateway endpoints for S3 and DynamoDB are completely free with no per-GB or hourly charges. Interface endpoints for all other AWS services cost $0.01 per GB of data processed plus $0.01 per hour per AZ in us-east-1. An Interface endpoint across 3 AZs costs $21.90/month in hourly charges alone ($0.01 x 730 hours x 3), plus per-GB fees. Always use Gateway endpoints where available.
How do hidden costs affect my real egress rate?
Add up the meters a byte passes through. In us-east-1, a byte that leaves through an Application Load Balancer (about $0.008/GB when processed bytes set the LCU count), crosses an AZ to reach a NAT Gateway ($0.01/GB), is processed by the NAT Gateway ($0.045/GB) and then goes to the internet ($0.09/GB for the first 10 TB) costs about $0.153/GB, 70 percent above the headline egress rate. The multiplier depends on your architecture: multi-AZ deployments with NAT Gateways see the highest hidden cost multipliers. Single-AZ deployments with VPC Gateway Endpoints have the lowest, but sacrifice availability.
How can I audit my architecture for hidden egress costs?
Start by reviewing your AWS Cost Explorer filtered by 'Data Transfer' charges. Look for NAT Gateway processing fees under the VPC section, cross-AZ charges appearing as 'Inter-AZ data transfer', and API Gateway data transfer charges. Enable VPC Flow Logs to understand traffic patterns between AZs. Check if you have VPC Gateway Endpoints enabled for S3 and DynamoDB. Review your load balancer data processing charges. Finally, audit NAT Gateway usage and consider alternatives like IPv6 or VPC endpoints for each traffic pattern.
All rates are us-east-1, checked against the AWS Price List API (AWSDataTransfer, AWSELB, AmazonVPC offer files) and aws.amazon.com/vpc/pricing on 13 November 2026.