Budget governance
Layer budgets on resources, groups and accounts, set the alert threshold that triggers a conversation, and keep the whole thing running rather than letting it quietly lapse.
5 lessons. 1 quiz.
Read in order, or jump to what you need.
Budget vs forecast vs alert
By the end of this lesson, you will be able to distinguish budget, forecast, and alert as three separate concepts; explain why budgets do not auto-enforce; and design each independently for your team's monthly cycle.
Per-resource, per-group, per-account budgets
By the end of this lesson, you will be able to pick the right budget scope for an accountability boundary, design a composite budget hierarchy, and explain why multiple budgets on the same data are independent (and useful).
Threshold-crossing notifications
By the end of this lesson, you will be able to pick a budget's alert threshold, route its warning and exceeded alerts to the right audience, and predict how often each channel will hear about it.
Green/yellow/red signals
By the end of this lesson, you will be able to read budget traffic-light signals at a glance, diagnose a red budget systematically, and propose the right corrective action by pattern.
Live computation, not stored
By the end of this lesson, you will be able to defend the architectural choice to compute budget spend live (rather than store a `current_spend_usd` column), predict the performance characteristics, and reason about why this choice matches the two-source cost model.
Module quiz.
Take it once the lessons are done.