- Newest
- Most votes
- Most comments
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#/
Thank you! I've already submitted a new case with Account Activation / Bedrock Allowlisting category and attached my EIN. Will update here once resolved.
Update: it has now been 6 days since I opened the support case, and it is still unassigned.
I also reached out through X/Twitter, which is the only place where I was able to get any response at all. However, the actual case remains unresolved.
At this point, it seems that unless I pay for a support plan, there is no practical path to getting an AWS-side provisioning/quota issue reviewed.
This is especially frustrating because the problem does not appear to be caused by customer misconfiguration. The account is activated, the organization is created, the model subscription is in place, and the same throttling behavior happens across multiple regions on the very first request.
If there is a required activation step for new Bedrock accounts that is not visible in the console, I would appreciate a clear answer. Otherwise, this looks like a platform-side issue that should not require a paid support subscription just to be acknowledged.
