Pay-as-you-go pricing means you are charged for what runs, whether or not anyone is using it. Most unexpected cloud bills are not caused by success; they are caused by things left switched on.
The usual culprits
- Development and staging environments running at full size overnight and at weekends.
- Volumes and snapshots that outlived the instances they belonged to.
- Load balancers and reserved addresses provisioned for a test.
- Log and metric retention set to “forever” by default.
- Data transfer, especially egress and cross-region traffic.
- Instances sized for a peak that never arrived.
Controls worth putting in place immediately
- A billing alert at a threshold that would genuinely surprise you.
- Mandatory tags for project, environment and owner, enforced in your tooling.
- A schedule that stops non-production resources outside working hours.
- Lifecycle rules on storage and retention limits on logs.
- A monthly review of the largest line items.
None of these requires a cost management platform. They require deciding once and automating.
Commitments come after stability, not before
| Mechanism | Appropriate when |
|---|---|
| On-demand | Usage is still changing, or workloads are short-lived. |
| Committed use or reserved capacity | Baseline has been stable for months. |
| Spot or preemptible capacity | Work is interruptible and checkpointed. |
| Savings on storage class | Access patterns are understood and measured. |
Committing before you know your steady state locks in an estimate. Measure for a quarter, then commit to the floor you are confident about and leave the variable part on demand.
Give cost an owner
Costs that belong to everyone belong to no one. Assign each project an owner who sees its spend monthly and can explain it. That single change usually does more than any tooling, because it turns an abstract number into someone’s responsibility.
Summary
Alert, tag, schedule shutdowns, expire storage and review monthly. Commit to discounts only once the baseline is proven. Cost control on usage-based billing is a habit, not a project.
