AWS Bedrock Silently Kills Claude Opus 4.7 Quota: A Warning for Production AI Workflows

A Hacker News user reports that their Claude Opus 4.7 model access was suddenly revoked on Amazon Bedrock, with the TPM quota silently set to 0. The user, who relies on the model for production workflows serving government customers, encountered throttling errors before receiving an explanation from AWS support.

According to the support response, the quota drop occurred due to a “recent system update” that adjusted access controls based on factors including regional considerations, payment history, and usage patterns. Quotas were set to 0 starting May 1st, 2026, and AWS explicitly states that restoration “cannot guarantee approval.” The recommended workaround: migrate to Claude Opus 4.6, for which the user has quotas of 10,000 requests/min and 3,000,000 tokens/min in us-east-1 (with cross-region and global variants). The support message notes that Opus 4.6 “can serve as an effective replacement with minimal code changes.”

HN commenters express frustration. User DetroitThrow calls this “insane for a company to pull this crap on paying customers with production workflows” and recommends switching to Google AI or direct Anthropic access. They note that Bedrock has a history of random throttling, citing Quinnypig‘s previous coverage of enterprise support rug-pulls. The original poster confirms they “can no longer make even a single request.”

This incident underscores the risk of relying on AWS Bedrock for production AI inference, especially with frontier models where access can be revoked without notice. Developers running mission-critical workloads on Bedrock should consider multi-provider fallbacks or direct API contracts with model providers like Anthropic.