Amazon Redshift Rate Limits
Amazon Redshift exposes three API surfaces - the Redshift control-plane (CreateCluster, DescribeClusters), the Redshift Data API (ExecuteStatement, GetStatementResult), and the Serverless control-plane. All follow standard AWS API throttling per account/region. Cluster-level concurrent connection limits and query-queue concurrency are enforced at the database level. Use exponential backoff with jitter on ThrottlingException.
Amazon Redshift Rate Limits is the machine-readable rate-limit profile for Amazon Redshift on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring varies, concurrent_connections, and concurrent_queries.
Limit state is signalled in the requestId and retryAfter response headers, and an exhausted limit returns HTTP 400.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include Rate Limiting, Data Warehouse, and Redshift.
requestIdretryAfter
generated, dated 2026-05-05.
Limits
Policies
Sources
- https://docs.aws.amazon.com/redshift/latest/mgmt/amazon-redshift-limits.html
- https://docs.aws.amazon.com/redshift-data/latest/APIReference/Welcome.html
- https://docs.aws.amazon.com/general/latest/gr/api-retries.html
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.