Cutting Cloud Egress Costs with Private Interconnects
Moving data into a public cloud is usually free. Moving it out — to users, to your data centre or to another cloud — is not. For data-heavy workloads, egress can quietly become one of the largest items on the monthly bill.
Where egress comes from
- Backups and replicas copied back to on-premise storage
- Analytics and reporting tools pulling data out of cloud warehouses
- Applications split between cloud and data centre that talk constantly
- Traffic between two clouds in a multi-cloud setup
Four ways to reduce it
- Use a private interconnect. Cloud providers generally charge lower per-GB rates for data leaving over Direct Connect, ExpressRoute or Interconnect than over the internet. At scale the saving can pay for the circuit.
- Keep chatty components together. Place an application and its database in the same environment so they do not cross a billed boundary on every request.
- Compress and deduplicate backups and replication streams.
- Use caching and CDNs for content served to end users.
Measure first
Use the cloud provider’s cost and usage reports to identify which services and destinations generate egress before changing architecture. Often a handful of flows account for most of the cost.
Our Multi Cloud Connect team models your traffic and egress costs before recommending a design. Request a cost review.
