Bedrock batch inference job in terminal failure state
- Severity
- Low
- Service
- Bedrock
- Check ID
- BEDROCK_ZOMBIE_BATCH_JOB
What this check finds
A Bedrock batch inference job is in an Expired or Failed state. Failed jobs represent wasted token costs and potentially incomplete data processing. Expired jobs timed out in the queue and need resubmission.
Passing looks like: No failed Bedrock batch jobs lingering.
How to fix it
Review the failed job for errors, then delete or resubmit as appropriate. Bedrock console → Batch inference → select job → view failure reason.
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
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 AWS Budget alert configured for Bedrock spend