- Newest
- Most votes
- Most comments
Based on the information provided, there are a few important points to consider regarding your Claude 3.5 Sonnet V2 On-demand InvokeModel requests and the 429 errors you're experiencing:
-
The quota you've mentioned (L-79E773B3) with an applied value of 1 and a default value of 50 is not adjustable. This means you cannot request an increase for this specific quota through the standard quota increase process.
-
The 429 errors you're encountering may indeed be related to quota limits, but it's not necessarily the sole reason. These errors typically indicate that you're exceeding the allowed request rate.
-
Cross-region inference itself is not likely to be the direct cause of 429 errors. However, it's possible that cross-region requests might have different quota limits or be subject to additional constraints compared to same-region requests.
-
For Claude 3.5 Sonnet V2, the current inference quota is 50 requests and 400,000 tokens per minute. This quota is not adjustable at the moment.
-
Regarding requesting a quota increase for on-demand cross-region inference models, unfortunately, if the quota is marked as "Not adjustable," there isn't a standard process to request an increase through the Service Quotas console.
Given these points, here are some recommendations:
-
Double-check all your quotas related to Amazon Bedrock and Claude 3.5 Sonnet V2 in the Service Quotas console, as there might be other quotas affecting your usage.
-
Implement retry logic with exponential backoff in your application to handle occasional 429 errors gracefully.
-
If you consistently need higher throughput, you might want to explore other model options that support Provisioned Throughput, although this isn't currently available for Claude 3.5 Sonnet.
-
As suggested in the quota description, if you have ongoing concerns or questions about the non-adjustable quota, the best course of action would be to contact AWS Support directly. They may be able to provide more specific guidance or escalate your case if necessary.
-
Consider optimizing your application to work within the current quota limits, such as batching requests or implementing client-side rate limiting to stay within the 50 requests per minute limit.
Sources
AWS Bedrock Claude 3.5 Sonnet throttled randomly "Too many tokens, please wait before trying again." | AWS re:Post
Understand why there are service quotas on my account | AWS re:Post
Submit quota increase | AWS re:Post
answered 2 years ago
- As I have included in my question Applied account-level quota value: 1 AWS default quota value: 50
Here I believe limit would be 1 per minute for me I'd like to extend it to 50 2. I'll work in graceful fallbacks 3. Ok 4. I'd reach out to support for point 1. 5. Let's see how conversation with support goes
Relevant content
asked 2 years ago
asked a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago

Did you got any resolution on this? A lot of people are complaining about the same issue.