Egress fees are the cloud cost item that almost never appears in design-stage business cases and almost always appears as the largest surprise in production invoices. Across 340+ engagements, egress runs 4–11% of total cloud spend on multi-region or hybrid architectures, and almost half of that is negotiable through credits, committed-volume discounts and architectural changes. The customers who model egress at architecture time and negotiate it at commit time produce 30–55% reduction on the egress line.
Cloud egress is not a single charge — it is a stack. AWS, Azure and GCP all charge for inter-region transfer (data leaving one region for another within the same cloud), inter-AZ transfer (data crossing availability zone boundaries within a region), and internet egress (data leaving the cloud to the public internet or to a private connection). The published rates are similar across hyperscalers: roughly $0.02–$0.09 per GB for internet egress depending on volume and region, $0.01–$0.02 per GB for inter-region, and $0.01 per GB for inter-AZ. The aggregate matters because high-volume architectures often pay all three on the same logical operation.
A specific common case: a multi-region active-active architecture with cross-region replication, fronted by a CDN with origin in one region, serving traffic globally. The byte travels inter-region (replication), inter-AZ (load balancer to instance), and then egresses to the internet (CDN cache miss). Each leg is charged. The composite egress cost on this architecture often runs 14–22% of total cloud spend, not the 4–11% portfolio average.
The architecture is paying for transfer the design did not anticipate. Both the contract and the topology need attention.
All three hyperscalers offer egress-specific commercial mechanisms that are not part of standard pricing. AWS offers egress credits as part of EDP and PPA negotiations, and the AWS Pricing 100GB free egress per month tier (free egress for customers leaving AWS) is a specific feature aimed at regulatory commitments rather than a routine pricing change. Azure includes egress reduction within MACC programme funding and has bilateral committed-bandwidth pricing through ExpressRoute and dedicated routes. GCP offers the most published egress flexibility, including tiered network pricing and committed network throughput, with discount levels often reaching 35–50% off list at committed volumes.
The customer who arrives at commitment negotiation with a documented egress profile — top 10 destinations, top 10 paths, top 10 services causing egress — receives offers that the customer who arrives with "we want lower egress prices" never sees. Specificity is leverage — and folding that egress profile into a wider AWS EDP negotiation is how the credits get committed in writing rather than promised verbally.
The egress modelling template, the credit triggers, and the architectural patterns that reduce structural egress.
Contract discounts have a ceiling. Architectural changes have more durability. The patterns that most reliably reduce egress in production:
Egress credits and committed-volume pricing are negotiable — but only if asked for with specificity.
We have reduced egress lines by 30–55% across AWS, Azure and GCP customers — through both contract and architecture.
Weekly compliance intelligence for IT leaders.