- Newest
- Most votes
- Most comments
I apologize for the inconvenience you're experiencing with AWS Bedrock and Sonnet 3. The error you're encountering is indeed a throttling error, which typically occurs when the service is experiencing high demand or when account quotas are exceeded. However, it's unusual for this to persist for 48 hours.
Here are some steps you can take to address this issue:
-
Check your Amazon Bedrock service quotas in the AWS Service Quotas console. This will help you understand the limits allocated to your account.
-
Implement a retry mechanism with exponential backoff and random jitter in your code. This is an AWS recommended approach for improving reliability when dealing with throttling errors.
-
If you have high throughput requirements, consider exploring Provisioned Throughput for your use case. This can provide more consistent performance.
-
If your workload traffic consistently exceeds your account quotas, you may need to request a quota increase. You can do this by contacting your AWS account manager or AWS Support.
-
Try using the service in a different AWS region if possible, as the issue might be specific to the region you're currently using.
-
Verify that your AWS credentials are correct and up to date.
If the problem persists after trying these steps, it's advisable to contact AWS Support directly. They can investigate why you're experiencing this prolonged service disruption, especially since it's affecting your ability to meet the expected 99% SLA (Service Level Agreement).
Remember, while throttling errors are common for on-demand services, they shouldn't persist for extended periods like you're experiencing. AWS Support will be best equipped to provide a more detailed explanation of what's happening with your specific account and the Bedrock service.
Sources
Troubleshooting Amazon Bedrock API Error Codes - Amazon Bedrock
Troubleshoot the "503 Service Unavailable error" | AWS re:Post
Thanks for your quick response. As I mentioned, I don't use this service and has not reached my quote for sure, please check the picture, I am just trying to ask one question from playground or code. I am not using this service in the product currently and just want to test.
Relevant content
- Accepted Answerasked 3 months ago
- Accepted Answerasked 13 days ago
- asked 2 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 6 months ago
Hi there,
I'm Dennis, a Developer Advocate at AWS. I'm really sorry about the trouble this caused and want to thank you for highlighting the issue. We're aware of the problem and are actively working on a resolution.
I'd like to help you directly with this matter. For privacy reasons, it would be best if you could reach out to me via my official Amazon email at traubd@amazon.com or a DM on LinkedIn: https://www.linkedin.com/in/dennis-traub/
I can then gather more details and personally look into your case.
Thanks again, your feedback helps us fix things faster and better!
Dennis
I just realized I used my Builder ID. Switched to my internal AWS profile here on re:Post now. To double-check, click on my name above this comment to confirm I'm legit :-)