The Register reported on May 18, 2026 that some AWS and Google Cloud customers received unexpected AI bills ranging from thousands to tens of thousands of dollars. On Google Cloud, one user reported a $127,000 bill he attributes to a brute-forced API key, and another reported a $10,000 bill despite a $250 spending cap. Google refunded two affected users, with charges of $17,000 and $10,000, and said it would review more accounts. On AWS, a startup using Bedrock with credits was billed roughly $30,000 to $38,000 when he expected hundreds.
The AWS case shows how cost controls can have gaps. AWS Cost Anomaly Detection did not alert because Bedrock charges were billed through AWS Marketplace, which the tool does not cover, and billing switched from credits to cash when the credits ran out. AWS said it has no plans to change the policy. As businesses add AI features, usage-based charges can grow much faster than traditional cloud spend.
Ask whoever manages your cloud accounts to confirm that budget alerts and spending caps cover AI services specifically, including anything billed through a marketplace. Keep API keys out of public code and websites, rotate them regularly, and limit what each key can access. For new AI projects, consider whether buying directly from the AI vendor with hard spending limits is safer than consuming it through a cloud bill.
Treat AI services like any metered utility: set a budget, monitor it weekly at first, and know who gets the alert when it is exceeded.
Sources
Does this affect your business?
Our advisors can help you figure out the right move, at no cost.