- Newest
- Most votes
- Most comments
Hello.
New AWS accounts may have low Bedrock quotas.
The following URL contains relevant questions.
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
If the issue is related to quotas, it cannot be resolved by the user, so please contact AWS Support and open a case under "Account and billing".
https://console.aws.amazon.com/support
When making an inquiry, please select a category as follows:
Incidentally, the model access mentioned in re:Post Agent's AI automated response feature has already been discontinued and cannot be used.
https://aws.amazon.com/blogs/security/simplified-amazon-bedrock-model-access/
Based on the error you're experiencing with Amazon Bedrock, it appears you're encountering access or configuration issues with your newly created account. Here are some common reasons and solutions for exceptions when using Bedrock models:
Common causes for Bedrock exceptions:
-
Model Access Not Enabled: You need to explicitly request access to foundation models in Amazon Bedrock. By default, models are not automatically available in new accounts.
-
Insufficient IAM Permissions: Your IAM user or role may lack the necessary permissions to invoke Bedrock models. You'll need permissions like
bedrock:InvokeModelorbedrock:InvokeModelWithResponseStream. -
Region Availability: Amazon Bedrock is not available in all AWS regions. Ensure you're operating in a supported region.
-
Service Quotas: New accounts may have default service quotas that could be causing throttling or access issues.
Recommended steps to resolve:
- Navigate to the Amazon Bedrock console and request access to the specific models you want to use under "Model access" in the console
- Verify your IAM permissions include the necessary Bedrock policies
- Confirm you're using a region where Bedrock is available
- Check the AWS Service Quotas console for any limits that might be affecting your account
Without seeing the specific error messages in your screenshot, these are the most common issues with new Bedrock accounts. If problems persist after checking these items, I'd recommend reviewing the detailed error messages or contacting AWS Support for account-specific assistance.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated a year ago

There is no quota issues at all. Created new account 15 dyas back and recently firstly started using bedrock play ground.
Service quotas may be set lower than the displayed value, so please contact AWS support for assistance. https://repost.aws/questions/QUK8qnLwJRQhOPV58H0sC41Q/bedrock-too-many-requests-please-wait-before-trying-again