HTTP 503
An HTTP status code indicating that the server is temporarily unavailable, typically due to overload or maintenance; clients can retry with exponential backoff.
Timeline (last 90 days)
HTTP 503 indicates temporary unavailability on the provider side and is usually unrelated to call frequency; 429 indicates the caller exceeded the per-unit-time quota, and the response headers often carry Retry-After. 503 is suited to exponential backoff retries, while 429 is better handled by switching to a backup model or deferring to the next period.
AWS Bedrock documentation recommends retrying 503, while 429 requires checking the throttling configuration, because Bedrock quotas are tied to IAM policies.
HTTP status codes that should be retried include: 429, 502, 503, 504, as well as network-layer failures such as connection resets and timeouts.
All Facts (3)
HTTP 503 indicates temporary unavailability on the provider side and is usually unrelated to call frequency; 429 indicates the caller exceeded the per-unit-time quota, and the response headers often carry Retry-After. 503 is suited to exponential backoff retries, while 429 is better handled by switching to a backup model or deferring to the next period.
50%UnverifiedAWS Bedrock documentation recommends retrying 503, while 429 requires checking the throttling configuration, because Bedrock quotas are tied to IAM policies.
50%UnverifiedHTTP status codes that should be retried include: 429, 502, 503, 504, as well as network-layer failures such as connection resets and timeouts.
50%