Quotas and limits in Amazon Redshift
Amazon Redshift has quotas that limit the use of several resources in your Amazon account per Amazon Region.
There is a default value for each quota and some quotas are adjustable.
For adjustable quotas, you can request an increase for your Amazon account in an Amazon Region by submitting an
Amazon Redshift Limit Increase Form
Quotas for Amazon Redshift objects
Amazon Redshift has quotas that limit the use of several object types. There is a default value for each.
Quota name | Amazon default value | Adjustable | Description |
---|---|---|---|
Amazon accounts that you can authorize to restore a snapshot per snapshot |
20 |
No |
The maximum number of Amazon accounts that you can authorize to restore a snapshot, per snapshot. |
Amazon accounts that you can authorize to restore a snapshot per Amazon KMS key |
100 |
No |
The maximum number of Amazon accounts that you can authorize to restore a snapshot, per KMS key. That is, if you have 10 snapshots that are encrypted with a single KMS key, then you can authorize 10 Amazon accounts to restore each snapshot, or other combinations that add up to 100 accounts and do not exceed 20 accounts for each snapshot. |
Cluster IAM roles for Amazon Redshift to access other Amazon services |
501 |
No |
The maximum number of IAM roles that you can associate with a cluster to authorize Amazon Redshift to access other Amazon services for the user that owns the cluster and IAM roles. 1The quota is 10 in the following Amazon Web Services Regions: us-iso-east-1, us-iso-west-1, us-isob-east-1. |
Concurrency level (query slots) for all user-defined manual WLM queues |
50 |
No |
The maximum query slots for all user-defined queues defined by manual workload management. |
Concurrency scaling clusters |
10 |
Yes |
The maximum number of concurrency scaling clusters. |
DC2 nodes in a cluster |
128 |
Yes |
The maximum number of DC2 nodes that you can allocate to a cluster. For more information about node limits for each node type, see Clusters and nodes in Amazon Redshift. |
Event subscriptions |
20 |
Yes |
The maximum number of event subscriptions for this account in the current Amazon Region. |
Nodes |
200 |
Yes |
The maximum number of nodes across all database instances for this account in the current Amazon Region. |
Parameter groups |
20 |
No |
The maximum number of parameter groups for this account in the current Amazon Region. |
RA3 nodes in a cluster |
128 |
Yes |
The maximum number of RA3 nodes that you can allocate to a cluster. For more information about node limits for each node type, see Clusters and nodes in Amazon Redshift. |
Redshift-managed VPC endpoints connected to a cluster |
30 |
Yes |
The maximum number of Redshift-managed VPC endpoints that you can connect to a cluster. For more information about Redshift-managed VPC endpoints, see Redshift-managed VPC endpoints. |
Grantees to cluster accessed through a Redshift-managed VPC endpoint |
10 |
Yes |
The maximum number of grantees that a cluster owner can authorize to create a Redshift-managed VPC endpoint for a cluster. For more information about Redshift-managed VPC endpoints, see Redshift-managed VPC endpoints. |
Redshift-managed VPC endpoints per authorization |
10 |
Yes |
The maximum number of Redshift-managed VPC endpoints that you can create per authorization. For more information about Redshift-managed VPC endpoints, see Redshift-managed VPC endpoints. |
Reserved nodes |
200 |
Yes |
The maximum number of reserved nodes for this account in the current Amazon Region. |
Schemas in each database per cluster |
9,900 |
No |
The maximum number of schemas that you can create in each database, per cluster.
However, |
Security groups |
20 |
Yes |
The maximum number of security groups for this account in the current Amazon Region. |
Single row size when loading by COPY |
4 |
No |
The maximum size (in MB) of a single row when loading by using the COPY command. |
Snapshots |
700 |
Yes |
The maximum number of user snapshots for this account in the current Amazon Region. |
Subnet groups |
20 |
Yes |
The maximum number of subnet groups for this account in the current Amazon Region. |
Subnets in a subnet group |
20 |
Yes |
The maximum number of subnets for a subnet group. |
Tables for |
9,900 |
No |
The maximum number of tables for the large cluster node type. This limit includes permanent tables, temporary tables, datashare tables, and materialized views. External tables are counted as temporary tables. Temporary tables include user-defined temporary tables and temporary tables created by Amazon Redshift during query processing or system maintenance. Views and system tables aren't included in this limit. |
Tables for |
9,900 |
No |
The maximum number of tables for the |
Tables for |
9,900 |
No |
The maximum number of tables for the |
Tables for |
20,000 |
No |
The maximum number of tables for the |
Tables for |
200,000 |
No |
The maximum number of tables for the |
Tables for |
200,000 |
No |
The maximum number of tables for the |
Tables for |
200,000 |
No |
The maximum number of tables for the |
Number of databases |
60 |
No |
The maximum allowed count of databases in an Amazon Redshift cluster. This excludes databases created from datashares. |
Timeout for idle or inactive sessions |
4 hours |
No |
This setting applies to the cluster. For information about setting the idle-session timeout value for a user, see ALTER USER in the Amazon Redshift Database Developer Guide. The user setting takes precedence over the cluster setting. |
Timeout for idle transactions |
6 hours |
No |
The maximum period of inactivity for an open transaction before Amazon Redshift ends the session associated with the transaction. This setting takes precedence over any user-defined idle timeout setting. It applies to the cluster. |
Stored procedures in a database |
10,000 |
No |
The maximum number of stored procedures. See Limits and differences for stored procedure support for more limits. |
Maximum number of connections for RA3 nodes |
2,000 |
No |
The maximum number of connections to an RA3 cluster. The maximum connections allowed varies by node type. |
Maximum number of connections for DC2 nodes |
Varies |
No |
The maximum number of connections to a dc2.large cluster is 500. The maximum number of connections to a dc2.8xlarge cluster is 2000. |
Number of Amazon Redshift roles in a cluster |
1,000 |
Yes |
The maximum number of Amazon Redshift roles that you can create per cluster. For more information about role-based access control (RBAC) roles see Role-based access control (RBAC) in the Amazon Redshift Database Developer Guide |
Quotas for Amazon Redshift Serverless objects
Amazon Redshift has quotas that limit the use of several object types in your Amazon Redshift Serverless instance. There is a default value for each.
Quota name | Amazon default value | Adjustable | Description |
---|---|---|---|
Number of databases |
100 |
No |
The maximum allowed count of databases in an Amazon Redshift Serverless namespace. This excludes databases created from datashares. |
Number of schemas |
9,900 |
No |
The maximum allowed count of schemas in an Amazon Redshift Serverless instance. |
Number of tables |
200,000 |
No |
The maximum allowed count of tables in an Amazon Redshift Serverless instance. |
Timeout for idle or inactive sessions |
1 hour |
No |
For information about setting the idle-session timeout value for a user, see ALTER USER in the Amazon Redshift Database Developer Guide. The user setting takes precedence. |
Timeout for a running query |
86,399 seconds (24 hours) |
No |
The maximum time for a running query before Amazon Redshift ends it. |
Timeout for idle transactions |
6 hours |
No |
The maximum period of inactivity for an open transaction before Amazon Redshift Serverless ends the session associated with the transaction. This setting takes precedence over any user-defined idle timeout setting. |
Number of maximum connections |
2000 |
No |
The maximum number of connections allowed to connect to a workgroup. |
Number of workgroups |
25 |
Yes |
The number of workgroups supported. |
Number of namespaces |
25 |
Yes |
The number of namespaces supported. |
Number of Amazon Redshift roles in a workgroup |
1,000 |
Yes |
The maximum number of Amazon Redshift roles that you can create per workgroup. For more information about role-based access control (RBAC) roles see Role-based access control (RBAC) in the Amazon Redshift Database Developer Guide |
For more information about how Amazon Redshift Serverless billing is affected by timeout configuration, see Billing for Amazon Redshift Serverless.
Quotas for Amazon Redshift Data API
Amazon Redshift has quotas that limit the use of the Redshift Data API. There is a default value for each. For more information about Amazon Redshift Data API, see Using the Amazon Redshift Data API.
Quota name | Amazon default value | Adjustable | Description |
---|---|---|---|
Transactions per second (TPS) for the |
20 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Transactions per second (TPS) for the |
3 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Transactions per second (TPS) for the |
100 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Transactions per second (TPS) for the |
3 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Transactions per second (TPS) for the |
30 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Transactions per second (TPS) for the |
20 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Transactions per second (TPS) for the |
3 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Transactions per second (TPS) for the |
3 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Transactions per second (TPS) for the |
3 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Transactions per second (TPS) for the |
3 |
No |
The maximum number of operation requests you can make per second without being throttled. |
Quotas for query editor v2 objects
Amazon Redshift has quotas that limit the use of several object types in your Amazon Redshift query editor v2. There is a default value for each.
Quota name | Amazon default value | Adjustable | Description |
---|---|---|---|
Connections |
500 |
Yes |
Maximum number of connections that you can create using the query editor v2 in this account in the current Region. |
Active principals per account |
50 |
Yes |
Maximum number of simultaneous principals who can use query editor v2 in this account in the current Region. |
Saved queries |
2,500 |
Yes |
Maximum number of saved queries that you can create using the query editor v2 in this account in the current Region. |
Query versions |
20 |
Yes |
Maximum number of versions per query that you can create using the query editor v2 in this account in the current Region. |
Saved charts |
500 |
Yes |
Maximum number of saved charts that you can create using the query editor v2 in this account in the current Region. |
Rows fetched per query |
100,000 |
No |
Maximum number of rows fetched per query by the query editor v2 in this account in the current Region. |
Data fetched size per query |
5 |
No |
Maximum size, in megabytes, of the data fetched per query by the query editor v2 in this account in the current Region. |
Maximum concurrent connections |
3 |
No |
Maximum database connections per user (includes isolated sessions). This value can be set from 1–10 by the query editor v2 administrator in Account settings. If you reach the limit set by your administrator, consider using shared sessions instead of isolated sessions when running your SQL. For more information about connections, see Opening query editor v2. For more information about setting the limit, see Account settings. |
Quotas and limits for Amazon Redshift Spectrum objects
Amazon Redshift Spectrum has the following quotas and limits:
-
The maximum number of databases per Amazon account when using an Amazon Glue Data Catalog. For this value, see Amazon Glue service quotas in the Amazon Web Services General Reference.
-
The maximum number of tables per database when using an Amazon Glue Data Catalog. For this value, see Amazon Glue service quotas in the Amazon Web Services General Reference.
-
The maximum number of partitions per table when using an Amazon Glue Data Catalog. For this value, see Amazon Glue service quotas in the Amazon Web Services General Reference.
-
The maximum number of partitions per Amazon account when using an Amazon Glue Data Catalog. For this value, see Amazon Glue service quotas in the Amazon Web Services General Reference.
-
The maximum number of columns for external tables when using an Amazon Glue Data Catalog, 1,597 when pseudocolumns are enabled, and 1,600 when pseudocolumns aren't enabled.
-
The maximum size of a string value in an ION or JSON file when using an Amazon Glue Data Catalog is 16 KB. The string can be truncated if you reach this limit.
-
You can add a maximum of 100 partitions using a single ALTER TABLE statement.
-
All S3 data must be located in the same Amazon Region as the Amazon Redshift cluster.
-
Timestamps in ION and JSON must use ISO8601
format. -
External compression of ORC files is not supported.
-
Text, OpenCSV, and Regex SERDEs do not support octal delimiters larger than '\177'.
-
You must specify a predicate on the partition column to avoid reads from all partitions.
For example, the following predicate filters on the column
ship_dtm
, but doesn't apply the filter to the partition columnship_yyyymm
:WHERE ship_dtm > '2018-04-01'
.To skip unneeded partitions you need to add a predicate
WHERE ship_yyyymm = '201804'
. This predicate limits read operations to the partition\ship_yyyymm=201804\
.
These limits don't apply to an Apache Hive metastore.
Naming constraints
The following table describes naming constraints within Amazon Redshift.
Cluster identifier |
|
Database name |
|
Endpoint name of a Redshift-managed VPC endpoint |
|
Admin user name |
|
Admin password |
|
Parameter group name |
|
Cluster security group name |
|
Subnet group name |
|
Cluster snapshot identifier |
|