No AWS Budget alert configured for Bedrock spend
- Severity
- High
- Service
- Bedrock
- Check ID
- BEDROCK_NO_BUDGET_LIMIT
What this check finds
No AWS Budget covering Amazon Bedrock model usage has been detected. Bedrock token costs can scale unexpectedly with usage spikes — a dedicated budget alert catches runaway spend before it becomes a large bill.
Passing looks like: AWS Budget alert for Bedrock spend configured.
How to fix it
Create a cost budget filtered to the 'Amazon Bedrock' service with an alert at your expected monthly threshold: AWS Budgets console → Create budget → Service = Amazon Bedrock.
AI risk mappings
| Framework | Controls |
|---|---|
| OWASP Top 10 for LLM Applications (2025) |
|
| MITRE ATLAS (Adversarial Threat Landscape for AI Systems) |
|
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
More Bedrock checks
- CriticalBedrock agent IAM role has broad permissions
- CriticalBedrock API key belongs to an administrator
- HighBedrock agent has no guardrail applied
- HighBedrock knowledge base not encrypted with CMK
- HighBedrock model invocation logging not enabled
- HighExternal model weights imported into Bedrock without governance review
- HighLong-lived Bedrock API key in use
- HighNo Bedrock guardrails configured