AWS Budgets
Spend thresholds with alerts and automated actions.
❓ What is it?
A service for setting cost and usage budgets that alert (email/SNS) at thresholds — including FORECASTED breaches — and can trigger actions like applying a restrictive IAM policy when a budget blows.
💡 Why does it exist?
A runaway training job or a token-hungry prompt loop can burn a month's budget overnight. Budgets convert billing surprises into early warnings and, if you choose, automatic brakes.
⏱️ When should you use it?
Set budgets per project/tag for experimentation accounts, alert at 50/80/100% (actual AND forecasted), and use budget actions to stop non-production spend from compounding.
🗺️ Where does it fit?
In the governance layer above all workloads; alerts flow to SNS so they can page humans or trigger Lambda cleanups.
🔌 How do you integrate it?
Create a cost budget scoped by tag or account, add alert thresholds and subscribers, and optionally attach an action (deny policy / stop instances) with an approval workflow.
🧩 Commonly integrated with
🎯 Exam angle (AIF-C01)
- Only Budgets ALERTS proactively (including on forecasts) — Cost Explorer just shows you charts.
- Budget ACTIONS (auto-applying restrictions) answer "prevent further spend automatically".