Why architecture matters here

Egress bills surprise teams late. Architecture matters because routes + mitigations + attribution compose.

Advertisement

The architecture: every piece explained

The top strip is routes. Cross-AZ. Cross-region. To internet. To another cloud.

The middle row is mitigations. VPC endpoints. CDN offload. Compression. Direct Connect.

The lower rows are ops. Attribution. Metrics. Ops — alerts + FinOps + review.

Cloud egress cost — data transfer + VPC endpoint + CDNsurprising line itemCross-AZcheap-ishCross-regionexpensiveTo internethighestTo another cloudeven moreVPC endpointsavoid public routeCDN offloadcache at edgeCompressionbrotli / gzipDirect Connectprivate linkAttributiontag traffic sourcesMetricsGB per teamOps — cost alerts + FinOps + design reviewroutecachecompresslinktagwatchwatchoperateoperate
Cloud egress: routes + mitigations to control cost.
Advertisement

End-to-end flow

End-to-end: service in us-east-1 calls S3 in same region via VPC endpoint — free. Serves static assets via CloudFront — cached, cheap. Analytics dump goes cross-region — costs. Team A owns bulk of egress; attribution enables charge-back.