logo
blogtopicsabout
logo
blogtopicsabout

Unexpected AI Costs Surface on AWS and Google Cloud

AIDeveloper ToolsAPICloudSecurity
May 18, 2026

TL;DR

  • •AI API abuse is leading to unexpectedly high cloud bills.
  • •Publicly exposed API keys are a major vulnerability, allowing unauthorized AI inference.
  • •Cloud providers are slow to issue refunds and improve preventative measures.

Cloud users are reporting unexpectedly large bills – reaching tens of thousands of dollars – due to unauthorized usage of AI services on both AWS and Google Cloud. These incidents highlight a growing problem with AI cost management and security vulnerabilities in cloud environments.

What Happened

The Register reports on two recent cases: one involving Google Cloud and another concerning AWS. In both instances, customers incurred substantial charges without prior notification from their cloud provider and experienced difficulties obtaining prompt resolution or refunds. The Google Cloud case centers around compromised API keys. Specifically, API keys that were historically recommended to be placed on the front end of applications (for attribution purposes) were later configured to also grant access to Google’s Gemini AI platform. This meant publicly accessible keys could be exploited to run expensive AI inference tasks, like using the Nano Banana and Veo 3 models, without authorization. The AWS case involved a user receiving a $30,000 invoice after using the Claude model through Bedrock.

Why It Matters

These incidents expose critical weaknesses in cloud security practices and the cost controls surrounding AI services. While cloud providers offer tools for managing API access and monitoring usage, the cases suggest these tools are either insufficient, not widely adopted, or not proactively configured to prevent abuse. For developers, this means a greater need for vigilance in securing API keys and carefully monitoring AI service usage. Enterprises relying on cloud-based AI must implement robust cost management strategies and audit their API key configurations. The lack of timely support and refund processes from the cloud providers exacerbates the problem, leaving customers to bear the financial burden of unauthorized activity. It is also unclear how widespread this problem is and whether it represents an isolated incident or a systemic flaw in cloud AI security.

What To Watch

It remains to be seen how AWS and Google Cloud will address these issues. Will they proactively refund affected customers? Will they improve their API key management guidance and tools? Will they offer more granular cost controls and real-time alerting for AI service usage? Developers and IT teams should closely monitor announcements from both providers and review their own cloud configurations to mitigate potential risks. The emergence of services like Truffle Security, which identified the Google Cloud vulnerability in February, suggests a growing market for specialized cloud security tools. The podcast, "The Kettle", from The Register, offers additional discussion on this topic and can be found at the link in the source material.

Source:

The Register ↗