AWS user faces a $30K–$38K Bedrock bill that cost-anomaly detection never flagged
AWS Bedrock customer (individual developer) · May 14, 2026 · General agent
What happened
A developer using Amazon Bedrock expected AWS Cost Anomaly Detection to catch runaway spend, but received a $30,000–$38,000 invoice after about a month of use. The Register reported that Bedrock bills through AWS Marketplace, which the cost-anomaly tool does not cover, so the account silently switched from credits to cash billing with no warning.
Causal vector
Provider-side billing blind spot — agent inference billed through a Marketplace path invisible to cost-anomaly detection
Source
Reported by The Register. Verified against the primary report.
Provider 'anomaly detection' is retrospective and scoped to specific billing paths. A spend firewall enforces the ceiling before the model is called — a daily total or velocity limit returns BLOCKED the moment cumulative agent spend crosses the bound, regardless of how the provider invoices.
The six rule types that contain this class of failure
Per-transaction cap
Any single spend above your ceiling is BLOCKED before it moves.
Daily total
Cumulative spend across all agent calls, bounded per day.
Velocity limit
Stops runaway retry loops — the #1 cause of overnight losses.
Merchant allowlist
Only approved destinations can ever receive funds.
Category rules
Flag high-risk classes (crypto, infra, refunds) for review.
Approval threshold
Above a value, the action waits for a human.
Related incidents
Three-person agency hit with a $14,000 AWS Bedrock bill after attackers burn stolen keys on Claude
Amazon Bedrock (customer: three-person agency) · Jul 16, 2026
Stolen Google Cloud API keys run up $3K–$127K Gemini bills for developers
Google Cloud customers (multiple developers) · May 13, 2026
Gartner: worldwide AI spending forecast at $2.52 trillion in 2026, up 44% YoY
Gartner / Portal26 · Jan 1, 2026
Don't be the next entry
Every incident in this database is the result of trusting a prompt, a provider cap, or a human review cycle. sipi.bot replaces all three with one deterministic call. 67 documented failures, one control.