Amazon Bedrock 0 invoke quotas
Hi, I'm experiencing a problem with Amazon Bedrock. Since yesterday (22.10.2024) I'm getting Too many requests error from Invoke model endpoint. Though there was just one request:
So I've navigated to services quotas tab to take a look on what might be the issue, and surprisingly found that all on-demand invoke quotas are set to zero (Claude instant v1 is the model I'm using):
Even though the model access is activated:
A couple of days before it worked perfectly. And now I'm not able to invoke a model even within a playground due to same Too many requests error. Could you please advise for possible errors or if AWS did something recently?
- Newest
- Most votes
- Most comments
I apologize for the inconvenience you're experiencing with Amazon Bedrock. Based on the information you've provided, it seems you're encountering an unusual situation with your service quotas for the Invoke model endpoint.
The "Too many requests" error you're receiving, despite having only one request, coupled with the on-demand invoke quotas being set to zero, indicates a potential issue with your account's service quotas or a temporary service disruption.
Here are a few steps you can take to troubleshoot and potentially resolve this issue:
-
Double-check your AWS Region: Ensure that you're trying to invoke the model in the same AWS Region where you have been granted access. Model support can vary by region.
-
Verify your IAM permissions: Make sure your IAM user or role has the necessary permissions to invoke the model. The required permissions include "bedrock:InvokeModel" and "bedrock:InvokeModelWithResponseStream".
-
Check for any account restrictions: There might be a security restriction on your AWS account. If this is the case, you may need to open a support case with AWS Support.
-
Service quota increase request: Although unusual, if your quotas have indeed been set to zero, you should request a service quota increase through the AWS Support Center.
-
AWS Service Health Dashboard: Check the AWS Service Health Dashboard to see if there are any ongoing issues with Amazon Bedrock in your region.
-
Contact AWS Support: If none of the above steps resolve your issue, it's recommended to contact AWS Support directly. They can investigate why your quotas might have been set to zero and help resolve any account-specific issues.
Given that this worked a few days ago and suddenly stopped working, there's a possibility of a recent change or temporary issue on the AWS side. AWS Support would be best positioned to provide specific information about any recent changes or to investigate why your quotas appear to be set to zero.
Remember, service quotas are typically not set to zero for active accounts, so this situation is unusual and warrants further investigation by AWS Support.
Sources
AWS re:Post Knowledge Center Spotlight: Amazon Bedrock | AWS re:Post
Resolve InvokeModel API error in Amazon Bedrock | AWS re:Post
ResponseStream - Amazon Bedrock
Relevant content
- AWS OFFICIALUpdated a year ago
