- Newest
- Most votes
- Most comments
Throttling is there as part of helping to prevent surprisingly large bills. You need to establish a pattern of AWS usage. I suggest you provision a free-tier EC2 instance.
Hello.
Below is a question from someone who is experiencing the same problem as you.
According to the response, it seems that communication with AWS support will be necessary.
https://repost.aws/ja/questions/QUf16LkLwNS2yRbKVufdu6FA/new-account-stuck-at-0-tpm-rpm-for-all-bedrock-models-despite-aws-default-showing-5-000-000-tpm-provisioning-issue
Please contact AWS support via the following URL.
When making an inquiry, I recommend selecting a category as shown in the image below.
https://support.console.aws.amazon.com/support/home#/
I understand you're experiencing ThrottlingException errors across all Amazon Bedrock models in us-east-1, with your Service Quotas showing 0 applied quota. This situation typically indicates that your account doesn't have the default quotas provisioned yet.
Here are the steps to resolve this:
Immediate Actions:
-
Verify your quota increase request status - Since you mentioned submitting a request on April 11, 2026, check the Service Quotas console to see if it's still pending or if there are any updates. Quota increase requests typically require review and approval.
-
Contact AWS Support directly - Given that you're seeing 0 applied quota across all models, this appears to be an account-level provisioning issue rather than hitting actual limits. Open a support case through the AWS Support Center, providing your Account ID and the specific details you've shared. Support can investigate why default quotas aren't showing and expedite the resolution.
-
Check for account restrictions - Verify in the AWS Billing and Cost Management console that there are no service control policies or organizational restrictions that might be blocking Bedrock access.
-
Try a different region temporarily - While your primary issue is in us-east-1, testing in another region (like us-west-2) can help determine if this is region-specific or account-wide.
Important Notes:
- The "0 applied quota" is the key indicator that default quotas haven't been provisioned for your account
- Even with an active payment method, new accounts or accounts new to Bedrock may require explicit quota approval
- ThrottlingException with immediate failures (even on simple requests) confirms this is a quota provisioning issue, not usage-based throttling
AWS Support is your best path forward to get the account-level access enabled, as they can directly provision the necessary quotas for your account.
Relevant content
- asked a month ago
- AWS OFFICIALUpdated 8 months ago

Thanks you very much !