Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

[provisioning bug] - AWS Bedrock account-level quota for new account is set to 0 for every model.

-1

As title suggests, my model quotas on Bedrock are all set to 0, this includes every Antrophic model. I guess it's a provisioning bug and my account wasn't properly seeded to default values, thus i get ThrottlingException: Too many tokens per day error on every prompt.

To avoid some useless AI generated responses:

  • already submitted my use-case for antrophic models and got access.
  • account is properly funded with enough credits.
  • I've never used any of these models before, this is a fresh account.
  • already submitted a ticket to support, this post is just additional measure to get it fixed hopefully

I guess there is nothing much i can do but wait for support?

Topics
Machine Learning & AIGenerative AI on AWS
Tags
Service QuotasAccount SupportAmazon Bedrock
Language
English

asked a month ago186 views

2 Answers
0
Accepted Answer

So anybody who is having this issue on fresh account

After 4-5 days of back and forth with support, they refused to increase quota because of low overall activity on the account, so expect that you will get refused as well.

Note that this only applies to new accounts.

answered a month ago

0

You're correct that this appears to be an account provisioning issue, and waiting for AWS Support to resolve it is the appropriate course of action. Since you've already submitted a support ticket, that's the right path forward.

While you wait, here are a few things to verify:

  1. Model Access Status: Double-check in the Bedrock console that your model access requests show as "Access granted" rather than "In progress" or "Access required." Even though you mentioned you got access, it's worth confirming the status is fully reflected in your account.

  2. Region Selection: Ensure you're operating in a region where Bedrock and your desired models are available. Model availability and quotas can vary by region.

  3. Service Quotas Console: Check the Service Quotas console for Amazon Bedrock to see if the quotas are indeed showing as 0. This can help support diagnose the issue more quickly if you haven't already included this information in your ticket.

Unfortunately, account-level quota issues like this typically require intervention from AWS Support, as they involve backend provisioning that customers cannot modify directly. The support team should be able to investigate why your account wasn't provisioned with the default quota values and correct this for you.

If your support case isn't progressing quickly enough, you might consider escalating the ticket or requesting a callback if that option is available in your support plan.

answered a month ago

AWS
EXPERT

reviewed a month ago

EXPERT

reviewed a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content