Skip to content
Documentation menu

Troubleshooting

Every error code is also listed in the API reference.

Subscribing

ProblemFix
Error page after Set up your accountStart again from Set up your account in the AWS Marketplace console
Claim fails: linked to another accountSign in with the account that claimed it, or contact support
Stays pending for over an hourContact support with your AWS account ID

Connecting your AWS account

Message after Test and saveFix
"We couldn't assume this role"Wait for CREATE_COMPLETE, check the Role ARN, or relaunch
"The role works, but it can't list Amazon Bedrock models"The role was edited, or Bedrock is not available in that region

Calling the API

ProblemFix
401 invalid_api_keyThe key is wrong or revoked. Create a new one on API keys
403 bedrock_access_deniedThe stack (role AICloudGatewayRouter-...) was deleted or changed. Relaunch it
429 bedrock_throttledRetry with backoff, or raise your quotas in AWS Service Quotas
Times out before any outputUse stream: true for long answers
500 or 502Retry. If it persists, contact support

Models and routing

ProblemFix
403 bedrock_model_not_enabled, or no ClaudeEnable the models the dashboard lists
400 no_eligible_modelTrim the input, or enable more models
Turns of one conversation use different modelsExpected with auto. Pin a model to keep one

Budgets and guardrails

ProblemFix
403 budget_exceededRaise or remove the limit, or wait for 00:00 UTC on the 1st
Estimated spend differs from AWS billExpected: the estimate uses on-demand list prices
finish_reason is content_filterYour guardrail or the model's filter blocked it
403 bedrock_guardrail_deniedRelaunch the stack from AWS account, or remove the guardrail

Still stuck? See Support.

Full guide: troubleshooting.md on GitHub