Cloud
Cloud cost surprises and public budgets do not mix
Why variable cloud bills are a governance problem for agencies, and the controls that keep them predictable.
A private company can absorb a cloud bill that is twenty percent over forecast. A public agency has appropriated a specific amount for the fiscal year, and an overage means a budget adjustment, an explanation to the board, or an unpaid invoice. Cloud cost management is therefore a governance requirement, not an optimization.
The controls that matter
Tagging. Every resource carries the department, program, and environment that pays for it. Untagged resources are found and tagged weekly. Without this, no other control works.
Budgets and alerts. Budgets set by cost center with alerts at thresholds well before the limit, going to someone who can act.
Non-production scheduling. Development and test environments shut down outside working hours. This alone often cuts those environments' cost by more than half.
Rightsizing. Regular review of utilization and downsizing of oversized resources.
Storage lifecycle. Old backups and logs move to cheaper tiers or expire on a schedule aligned to retention rules.
Commitments. Reserved capacity or savings plans for the steady-state baseline, purchased after the environment has stabilized, not before.
Monthly review. A short meeting between IT and finance with a standard report: spend by department against budget, anomalies, and actions.
What we see go wrong
Experiments that were never turned off. Data transfer charges nobody modeled. Logging that captures everything forever. Backups of backups. All of these are preventable with the controls above.
Building it in
We set up tagging, budgets, and reporting as part of every landing zone before the first workload arrives. Adding cost controls after the environment has grown is much harder than starting with them.