No AWS Budget alert configured for this account
- Severity
- High
- Service
- Billing
- Check ID
- BUDGET_NOT_CONFIGURED
What this check finds
Without a Budget alert, unexpected cost spikes (from misconfiguration, a runaway process, or a security incident causing data exfiltration charges) go undetected until the monthly bill arrives. AWS Budgets are free for the first two budgets per account.
Passing looks like: AWS Budget alert configured.
How to fix it
Create a monthly cost budget with an alert threshold.
AWS CLI
aws budgets create-budget --account-id ACCOUNT_ID --budget file://budget.json --notifications-with-subscribers file://notifications.json
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
AWS Budgets → Create budget → Cost budget → set threshold at 80% and 100% of expected monthly spend.
Compliance
This is a cost check. It flags spend that buys nothing, which no compliance framework asks about, so it is not mapped to a control.
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs