The real cost of cloud egress (and how to avoid it)
Compute costs are visible. Storage costs are visible. Egress costs are the line item people scroll past without reading — until they're 20% of your bill.
Where egress comes from
- Public internet egress — data leaving the cloud to users. Typically $0.09/GB on AWS, $0.087/GB on Azure, $0.12/GB on GCP. The obvious one.
- Cross-region egress — data moving between regions. $0.02/GB on most clouds. Looks cheap until you realize active-active deployments can move terabytes daily.
- Cross-AZ egress — data between availability zones in the same region. $0.01/GB on AWS. Usually OK but can surprise chatty microservice deployments.
- NAT Gateway egress — every byte leaving a private subnet through NAT is charged twice: NAT processing ($0.045/GB) + public egress ($0.09/GB). Often more expensive than public egress directly.
How to find yours
Pull the last 90 days of billing and split by usage type. AWS: look for DataTransfer-Out-Bytes, DataTransfer-Regional-Bytes, and NatGateway-Bytes. Azure: Bandwidth line items. GCP: Cloud Egress under Networking.
Three moves that actually cut egress
1. Move static traffic to a CDN
CloudFront / Azure Front Door / Cloud CDN turn egress charges into CDN charges, which are cheaper per byte AND reduce origin egress. For any public-facing asset served more than a few times, this is free money.
2. Use VPC endpoints for managed services
Every byte going from your VPC to S3 / DynamoDB / SQS via the public endpoint is billed as egress. VPC endpoints keep that traffic on the private network for free.
3. Compress everything
gzip on HTML and JSON. Brotli for static files. Video? Confirm it's properly encoded. A 30% size reduction = 30% egress savings.
Tools
- Data Egress Cost Predictor — estimate before you commit to an architecture.
- Object Storage Price Comparator — R2 and Wasabi have zero egress fees and are a legitimate choice for download-heavy public assets.