1 min lesson
Compute hot spots and egress
Work through the cases in "Compute hot spots and egress", pairing each signal with the move that fits.
Step 1 of 2
Compute hot spots and egresswhere the big numbers hide
The most expensive idle in an AI shop, by far.
Bin-pack inference, scale to zero off-peak and alert on low utilization - an idle H100 is a five-figure monthly leak.
Preview/staging stacks that outlive their PR.
TTL labels plus a reaper that tears them down automatically.
Chatty services split across AZs pay per-GB both ways.
Use topology-aware routing to keep traffic in-zone where safe.
Cacheable responses hitting origin burn compute and egress.
Push a CDN in front; measure cache hit ratio before and after.
Every waste claim needs a before/after number. "Added a CDN, cache hit ratio went 0% to 82%, origin requests dropped 5x, egress fell $18K/mo" is a defensible win. "Added a CDN, should help" is a guess wearing a confident face - and an interviewer will ask for the number.