AWS Budgets

Cloud Financial Management

Set custom cost and usage thresholds, get alerted, and optionally trigger automated actions when spend crosses the line.

Verified against AWS documentation · 2026-08-28

Key facts

  1. 01Four budget flavors: cost, usage, RI utilization/coverage, Savings Plans utilization/coverage
  2. 02Alerts fire on actual OR forecasted spend — forecasted is the one that saves you before the damage is done
  3. 03Budget actions can auto-apply an IAM policy or SCP, or stop specific EC2/RDS instances — run automatically or after manual approval
  4. 04Data refreshes up to 3x/day (8–12 hours apart) — it's a smoke alarm, not a circuit breaker; spend can run for hours before a budget notices

Exam triggers

Phrases and scenarios that point here.

  • "Alert me when spending exceeds/is forecasted to exceed X" → Budgets, not Cost Explorer
  • "Automatically stop resources / restrict provisioning when a threshold is hit" → budget actions
  • "Notify before the bill arrives" → forecasted alert
  • Proactive threshold alerting → Budgets; historical analysis → Cost Explorer

Not this service

  • Analyze and visualize past spend → Cost Explorer
  • Anomaly detection with ML (unexpected spikes, no threshold set) → Cost Anomaly Detection
  • Itemized line-by-line billing data → Cost and Usage Report (CUR)

Use cases

  1. 01The classic student/sandbox guardrail: a $10 monthly budget with a forecasted alert at 80%, so a forgotten NAT Gateway pages you before it eats the month
  2. 02Per-team or per-project spend caps using tag or account filters — each squad's dev environment gets its own budget and its own alert
  3. 03A budget action that attaches a deny-provisioning IAM policy when a dev account hits 100% — spend freezes without anyone being awake
  4. 04RI/Savings Plans utilization budget alerting when usage drops below 80% — you already paid for the commitment, this tells you it's going idle
  5. 05Custom period budget matching a project or grant window (e.g., a 3-month migration), instead of forcing it into calendar months

How it's charged

  1. 01Budgets with alerts only (email/SNS) are free — no limit that matters in practice
  2. 02First two action-enabled budgets are free per month; each additional one is billed per day
  3. 03Action-enabled pricing is per budget, not per action — pile multiple actions on one budget at no extra cost
  4. 04Budget reports (scheduled email digests) are billed per report delivered — daily reports cost ~30x a monthly one
  5. 05Quotas: 20,000 budgets per account, 5 alerts per budget, 10 emails + 1 SNS topic per alert

Commonly confused with

AWS Cost ExplorerCloud Financial ManagementAWS Cost and Usage Report (CUR)Cloud Financial Management

References