You modeled compute. You modeled storage. You built cost estimates, ran capacity planning, and got sign-off on the architecture before a single resource was provisioned.
You did not model what it costs to move data.
Cloud egress is the tax that accumulates invisibly — not from a single expensive operation, but from thousands of small data movement events your architecture was never designed to account for. It shows up as a line item in the monthly bill that nobody owns, that nobody predicted, and that grows consistently as the system scales.
This guide covers what cloud egress costs actually are, where they come from, the architectural patterns that multiply them silently, and how to model them before the invoice arrives rather than after it does.
What Cloud Egress Actually Is
Egress is data leaving a cloud environment. Every time your system moves data — from a server to a user, from one region to another, from one availability zone to another — there is a potential cost event attached to it. Inbound data transfer (ingress) is almost always free. Outbound data transfer (egress) is almost always metered.
Three distinct egress categories — most architecture reviews only account for one:
Internet egress — data leaving the cloud provider entirely. This is the egress line item that appears in every cloud cost guide. It is also, for many architectures, not the largest egress cost.
Cross-region egress — data moving between two regions within the same cloud provider. For architectures with active multi-region deployments, this cost compounds quickly.
Cross-zone egress — the one most teams miss entirely until they see the bill. Availability zones within the same region are not free to communicate. AWS charges $0.01/GB in each direction for cross-AZ data transfer. In a microservice architecture spread across multiple AZs for high availability — as it should be — every inter-service call that crosses an AZ boundary is a billable event.
| Provider | Internet Egress (first 10TB) | Cross-Region | Cross-Zone | Free Tier |
|---|---|---|---|---|
| AWS | $0.09/GB | $0.02/GB | $0.01/GB each direction | 100GB/month |
| GCP (Premium Tier) | $0.08/GB | $0.01–0.08/GB | $0.01/GB | 1GB/month |
| GCP (Standard Tier) | $0.085/GB | $0.01–0.08/GB | $0.01/GB | 1GB/month |
| Azure | $0.087/GB | $0.02/GB | $0.01/GB | 5GB/month |
Rates vary by region, volume tier, and service. Check current provider pricing pages before budgeting.
Storage Is Cheap. Moving Data Out of It Isn't.
Object storage is one of the cheapest resources in the cloud. S3, GCS, and Azure Blob Storage charge fractions of a cent per GB per month for standard storage.
The cost is not in storing the data. It is in every system that reads it.
Analytics queries that scan large datasets pull gigabytes from object storage to compute on every execution. An ML training pipeline that reads training data from S3 into a GPU instance generates egress from storage to compute on every epoch. A data pipeline that copies data between storage tiers generates egress at every stage rather than transforming in place.
Storage is cheap. Moving data out of it isn't.
The architectural response: collocate compute with storage in the same region and AZ, query data in place with serverless analytics engines (BigQuery, Athena, Redshift Spectrum), and use caching layers to prevent repeated reads of the same data across pipeline stages.
Egress Multipliers
Most egress cost analyses focus on individual data transfer events. The real problem is architectural patterns that multiply egress — where a single user action, pipeline trigger, or retry event generates orders of magnitude more data movement than the operation itself warrants.
Fan-Out Architectures
A single inbound request triggers N downstream service calls, each of which pulls data from storage, calls an external API, or crosses a zone boundary. One user action becomes ten egress events. Ten concurrent users become a hundred. Fan-out architectures are correct designs for scalability — they become egress problems when the fan-out multiplier is never modeled against data transfer costs.
Retry Storms
A service encounters a transient failure and retries with the full request payload. At scale, retry storms generate egress volume that can exceed the original traffic by multiples — the same data transferred repeatedly without successful delivery. Retry logic without exponential backoff, jitter, or payload size awareness turns a brief service degradation into a sustained egress event.
Cross-Zone Microservice Chatter
Microservice architectures distributed across AZs for resilience generate inter-AZ traffic on every service-to-service call that crosses a zone boundary. A request chain that traverses five services across three AZs generates five potential cross-zone transfer events — each metered at $0.01/GB each direction. Zone-aware routing reduces this without sacrificing the availability architecture.
Data Duplication Pipelines
ETL and ELT pipelines that copy data between storage tiers — raw to processed, processed to curated — generate egress at every stage rather than transforming in place. A pipeline that copies 1TB through four stages transfers 4TB, not 1TB. The architectural alternative is transformation in place using serverless query engines.
Egress rarely comes from a single path. It comes from paths that multiply.
Where the Hidden Costs Live by Provider
AWS charges $0.01/GB in each direction for cross-AZ traffic within the same region — easy to miss because it appears as a line item shared across dozens of services. For microservice architectures with high inter-service call volumes across AZs, this compounds into significant monthly spend.
GCP's global VPC model eliminates many cross-zone cost traps that AWS architectures encounter. A single VPC spans all regions, and intra-region traffic between zones is cheaper than the AWS equivalent. The more significant GCP egress decision is Premium Tier versus Standard Tier — Premium Tier keeps traffic on Google's private backbone, Standard Tier routes via the public internet.
Azure follows a similar cross-zone model to AWS, with inter-AZ transfer metered within a region. Azure's ExpressRoute provides private connectivity with different egress economics for enterprise hybrid architectures with high on-premises-to-cloud data movement.
The provider comparison matters less than the architectural principle: wherever data moves across a billing boundary — zone, region, or provider — that movement has a cost, and that cost multiplies with request volume.
AI and Inference Egress: The New Problem
Inference pipelines have introduced an egress cost category that traditional architecture cost models were never designed to capture. An inference request that pulls retrieval context from object storage, queries a vector database in a different zone, calls an embedding model in a separate service, and returns a response has generated egress events at every step.
AI inference cost is the new egress. The principle established in cloud architecture for data movement — that cost emerges from behavior, not provisioning — applies directly to inference pipelines.
The architectural response is data gravity: run inference where the data lives. A GPU instance in the same AZ as the vector database it queries and the object storage it reads from eliminates the cross-zone egress events that accumulate invisibly in architectures where compute and data were placed independently.
How to Reduce Egress Costs
Egress cost reduction is an architecture exercise, not a FinOps exercise. The levers that actually move the number are design decisions.
1. Collocate compute and data. Place compute in the same region and AZ as the data it consumes. Zone-aware Kubernetes scheduling — topology spread constraints and affinity rules — reduces cross-zone chatter without changing the service architecture.
2. Query in place. Use serverless analytics engines — BigQuery, Athena, Redshift Spectrum — to run queries against data where it lives rather than pulling it to dedicated compute.
3. Cache aggressively. CDN caching eliminates internet egress for repeated requests. In-memory caching reduces cross-zone calls for frequently accessed data. Every cache hit is an egress event that did not happen.
4. Compress before transfer. High-ratio compression (zstd, Brotli) reduces egress volume by 60–80% for large dataset transfers. Binary serialization (Protocol Buffers, Avro) reduces inter-service payload size by 3–10x versus JSON.
5. Audit the multipliers. Before optimizing individual transfer rates, identify which architectural patterns are generating the highest egress volume. Fan-out patterns, retry storms, and cross-zone chatter are more valuable to fix than negotiating a lower per-GB rate.
Tool: Cloud Egress Calculator — model true data movement costs across AWS, Azure, and GCP. Whether you're migrating to a new provider, setting up multi-cloud disaster recovery, or running cross-region analytics — this exposes the hidden tiered pricing models before the bill arrives.
Architect's Verdict
Egress is not a billing problem. It is an architecture problem that surfaces as a billing problem after the system is in production and the design decisions that generated it are too expensive to reverse.
The teams that control egress costs are not the ones running tighter FinOps reviews. They are the ones who modeled data movement as a first-class architectural constraint at design time — who asked "what does this data transfer cost at 10x volume?" before the architecture was approved, not after the first invoice arrived.
The patterns that generate the largest egress bills are not misconfigurations. They are correct architectural decisions — high availability across AZs, fan-out for scalability, retry logic for resilience — made without egress as a design input.
Model it like compute. Model it like storage. It is the same tax, arriving from a direction you didn't expect.
Additional Resources
From Rack2Cloud:
- Cloud Architecture Strategy — platform selection, cost governance, and hybrid architecture decision framework
- Cloud Architecture Learning Path — structured progression from cloud fundamentals through advanced architecture patterns
- AI Inference Is the New Egress — how inference cost follows the same behavioral cost model as egress
- Cloud Cost Increases 2026 — the egress patterns driving unplanned spend increases
- Multi-Cloud Cascading Failure Risks — fan-out and cascade patterns in multi-cloud architectures
- GCP Cloud Architecture — GCP's global VPC model and cross-zone egress economics
- Cloud Egress Calculator — model your egress costs across AWS, Azure, and GCP
External:
- AWS Data Transfer Pricing — current AWS egress rates by region and service
- GCP Network Pricing — GCP egress pricing including Premium vs Standard Tier
Originally published at Rack2Cloud.com
Top comments (0)