Network & CDN efficiency
Networking cost hides in data movement: egress to the internet or across regions, NAT gateway data-processing charges, and content served from origin instead of a CDN edge. None of it shows up as a resource you can simply turn off — it’s about how traffic flows.
What we look for
Section titled “What we look for”- Egress paths — high cross-region or internet egress that a private endpoint, a co-located resource, or a different routing choice would reduce.
- NAT gateway inefficiency — duplicated gateways across zones, unbalanced traffic, or subnets that could reach a service privately instead of paying NAT data-processing.
- CDN cache efficiency — a low cache-hit ratio sending avoidable traffic back to origin, or content that should be cached at the edge.
These recommendations are review-oriented: they point at the path and the modelled saving, since the right fix depends on your architecture.
How to act
Section titled “How to act”leancosts surfaces the inefficient path, the evidence, and the modelled impact so the network owner can choose the fix — add a private endpoint, consolidate NAT gateways, tune cache rules. Follow Act on a cost finding.