Amazon Bedrock Quotas: 0 TPM 0 RPM

Your account's Bedrock quotas weren't seeded during provisioning — it's a known bug, not something you did wrong. There's no self-service fix; an AWS internal team needs to manually correct it.

Fastest paths to resolution:

Upgrade to Developer Support for actual engineer access Use live chat instead of creating cases Post on AWS re:Post with your case IDs Open a new case under "Account" (not Bedrock) framing it as a provisioning defect Until it's fixed, try toggling model access off/on or requesting a quota increase through Service Quotas — both can sometimes re-trigger the seeding process.

I understand your frustration with the quota situation in Amazon Bedrock. Based on your description, it appears your account wasn't properly provisioned with the default service quotas for Bedrock models, which is preventing you from using the service entirely.

Here are some steps and information that may help:

Understanding Bedrock Quotas: Amazon Bedrock has default quotas for throughput (tokens per minute/TPM and requests per minute/RPM) that vary by model and region. These quotas are typically applied automatically to accounts, but in rare cases, provisioning issues can occur.

Immediate Actions You Can Take:

1. Request Quota Increases via Service Quotas Console: Even though your current quota shows 0, you can still submit quota increase requests through the Service Quotas console. Navigate to Service Quotas → AWS services → Amazon Bedrock, find the specific model quotas you need, and request increases to at least the documented default values.

2. Try Alternative Support Channels: Since you have a new account with Basic Support and your cases are unassigned, consider:

• Using the AWS re:Post community for visibility from AWS experts
• Checking if your account has any billing or verification holds that might be affecting service provisioning
• Verifying your account is in good standing with no restrictions

3. Model Access: Ensure you've explicitly requested access to the models through the Bedrock console (Model access page), though this typically affects model availability rather than quota values.

For AWS Support Escalation: With Basic Support, response times can vary. If this is impacting business operations, you might consider temporarily upgrading to Developer or Business Support for faster response times and technical guidance. Business Support includes 24/7 access to Cloud Support Engineers and faster response times for production system issues.

The situation you're describing—where quotas show 0 instead of default values—is unusual and likely requires AWS internal investigation to resolve the provisioning issue with your account.