9.3 Cutting cloud cost without cutting service
You can take a real bill and find a defensible thirty percent.
Before:01. Cloud Foundations
Most cloud bills carry a defensible thirty percent of waste, and this topic is the method for finding it: right-sizing from actual metrics, sweeping idle resources, moving cold data to cold tiers, and fixing the architecture choices — egress, cross-zone chatter — that dominate cost. Commitment discounts come last deliberately: committing before usage is stable locks the waste in. It sits after visibility because cutting what you cannot attribute is guesswork. The confusion to resist is trimming instance sizes while ignoring architecture; the big money is in the shape of the system, not the size of its parts.
Work through these
Right-sizing from metrics; the idle-resource sweep
Resizing from measured usage and shutting down what nobody is using are the two cheapest wins available, and they are usually available. Doing the sweep once reveals how much was drifting.
Storage lifecycle and cold tiers
Data that is rarely read costs far less in a colder storage class, and lifecycle rules move it there without anyone remembering to. This is savings that continue after you stop paying attention.
Architecture choices that dominate cost (egress, cross-zone, chatty services)
Some costs are decided by architecture rather than configuration: data leaving the provider, traffic crossing zones, and services that chat more than they need to. No amount of resizing fixes these.
Commitment discounts once usage is stable, not before
Committing to a level of usage in exchange for a discount is sensible once usage is stable and expensive when it is not. The order matters: measure first, commit second.
Sign in to keep your progress.
Free resources
We haven't checked most of these for screen reader use yet.
Links last checked 29 Aug 2026.
Stuck here?
Ask a mentor. A real person answers, and they can see exactly which topic you're on. Usually within a couple of working days.
Checking your session…
Topics shown in module order.