Check the quotas your account actually has, per model and Region, weeks before launch. New accounts can start far below AWS's documented defaults. Request increases through Service Quotas, and bring in your AWS account team if you have one.
When you need this
- Requests return throttling errors at volumes below the documented quota.
- A launch depends on a newly released model.
- The account is new, or has no AWS account team.
Evaluation criteria
Know your applied quotas
What tokens-per-minute quota does the account actually have for each model and Region?
Look forCompare applied Service Quotas with documented defaults for each model's on-demand and cross-Region inference. Ziva received quotas 1,000 to 2,000 times below defaults. Proactive Ops received 5% of advertised levels. Startups on AWS credits report zero frontier-model quotas and increases denied for billing history.
Request early
Is the increase filed weeks before launch, with usage evidence?
Look forFile on-demand and cross-Region requests together with expected traffic and use case. AWS grants no increases for Legacy or deprecated models.
Route across Regions
Are requests going through a cross-Region inference profile?
Look forRoute through Geo or Global inference profiles to spread requests across Regions under a separate quota. On bedrock-runtime, Opus 5.5 needs them everywhere except London.
Reserve the floor
Is there steady traffic that cannot be throttled?
Look forCompare Reserved capacity, separate from on-demand quotas, with Provisioned Throughput on supported models. Reserved starts at 100,000 input and 10,000 output tokens per minute for 1 or 3 months.
Plan for revoked access
What happens if a model's quota drops to zero?
Look forKeep a tested fallback model in configuration. One government-serving team's Opus 4.7 quota dropped to zero overnight, and AWS could not guarantee restoration.
Retry without burning quota
Do client retries count against the quota you are short of?
Look forCap SDK retries and use backoff so one throttled request does not multiply.
Questions to ask vendors
- Who at AWS owns our quota requests, and what usage evidence do they need?
- Which models would we fall back to if a quota were cut?
- Do we qualify for the Reserved tier minimums?
- Are quotas for our launch model approved in every Region we route to?
Red flags
- A launch plan that assumes the documented default quota.
- One model and one Region with no fallback.
- SDK retries left at defaults during throttling.
- Discovering quota limits from production errors.
Products in this piece
Sources
- Official documentation
- 6
- Public source
- 6
- Amazon Bedrock User Guide: Quotas for the bedrock-runtime endpoint
- Amazon Bedrock User Guide: Service tiers
- Amazon Bedrock User Guide: Cross-Region inference
- Amazon Bedrock User Guide: Provisioned Throughput
- Amazon Bedrock User Guide: Model lifecycle
- Amazon Bedrock User Guide: Claude Opus 5.5 model card
- Ziva: 16 days, 4 channels, no AWS Bedrock quota fix (May 16, 2026)
- Proactive Ops: Amazon Bedrock Leaves Builders Stuck in 1st Gear (Feb 26, 2026)
- Hacker News: Claude Opus 4.7 quota suddenly changed to 0 TPM in Bedrock (May 1, 2026)
- r/aws: New account with quota 0 on Bedrock frontier models (Aug 9, 2026)
- r/aws: TPM quota increase request denied with no clear reason (Aug 29, 2026)
- Hacker News comment on Bedrock latency in legally required regions (Apr 21, 2026)