I want to troubleshoot the 503 Service Unavailable errors I receive when I use Amazon Bedrock on demand resources. I haven't exceeded the per AWS account limits.
Resolution
Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshoot AWS CLI errors. Also, make sure that you're using the most recent AWS CLI version.
Amazon Bedrock returns a 503 Service Unavailable error code for certain server-side exceptions.
A server-side exception is when the server is unable to respond because of failures or when there is a surge in the number of requests. This surge causes strain on shared resources. To determine the cause of this error, take the following actions:
Retry the request
To check if the error is a result of a temporary increase to API demand, the increased demand must be resolved. Use exponential backoff to retry the request. If you use AWS SDKs, then see Retry behavior.
Use another Region
To check if the demand increases or failures occur in one AWS Region, change the settings for your resources to use another AWS Region. When you change to a different Region, activate model access for Amazon Bedrock in that Region. If you use AWS SDKs, then see Compatibility with AWS SDKs.
To automatically route traffic across multiple Regions, activate cross-Region inference.
Use other foundation models
If the demand increases or failures occur on a specific foundation model, then other foundation models might operate without any issues.
Note:
Use Provisioned Throughput
Purchase Provisioned Throughput to provision a higher level of throughput. For more information, see Access Amazon Bedrock foundation models. For AWS management console, see Use a Provisioned Throughput. For AWS CLI or Python SDK, see Code examples for Provisioned Throughput in Amazon Bedrock. Available for Supported region and models for Provisioned Throughput.