Limits in Amazon Redshift
Quotas and Limits
Amazon Redshift has quotas that limit the total number of nodes that you can provision, and the number of snapshots that you can create; these quotas are per AWS account per region. Amazon Redshift has a default quota for each of these, which are listed at AWS Service Limits. If you attempt to exceed any of these quotas, the attempt will fail. To increase these Amazon Redshift quota limits for your account in a region, request a change by submitting an Amazon Redshift Limit Increase Form.
In addition to quotas, Amazon Redshift has limits for the following per-cluster values. These limits cannot be increased:
The number of nodes that you can allocate per cluster, which is based on the cluster's node type. This limit is separate from the limit for your AWS account per region. For more information about the current node limits for each node type, see About Clusters and Nodes.
The maximum number of tables, including temporary tables, that you can create per cluster is 9,900. Temporary tables include user-defined temporary tables and temporary tables created by Amazon Redshift during query processing or system maintenance. Views are not included in this limit. For more information about creating a table, go to Create Table Usage Notes in the Amazon Redshift Database Developer Guide.
The number of user-defined databases you can create per cluster is 60. For more information about creating a database, go to Create Database in the Amazon Redshift Database Developer Guide.
The number of schemas you can create per cluster is 9,900. For more information about creating a schema, go to Create Schema in the Amazon Redshift Database Developer Guide.
The number of concurrent user connections that can be made to a cluster is 500. For more information, see Connecting to a Cluster in the Amazon Redshift Cluster Management Guide.
A workload management (WLM) configuration can define a total concurrency level of 50 for all user-defined queues. For more information, go to Defining Query Queues in the Amazon Redshift Database Developer Guide.
The number of AWS accounts you can authorize to restore a snapshot is 20 for each snapshot and 100 for each AWS Key Management Service (AWS KMS) key. That is, if you have 10 snapshots that are encrypted with a single KMS key, then you can authorize 10 AWS accounts to restore each snapshot, or other combinations that add up to 100 accounts and do not exceed 20 accounts for each snapshot. For more information, see Sharing Snapshots in the Amazon Redshift Cluster Management Guide.
The maximum size of a single row loaded by using the COPY command is 4 MB. For more information, see COPY in the Amazon Redshift Database Developer Guide.
A maximum of 10 IAM roles can be associated with a cluster to authorize Amazon Redshift to access other AWS services on behalf of the user that owns the cluster and IAM role. For more information, see Authorizing Amazon Redshift to Access Other AWS Services On Your Behalf.
Naming Constraints
The following table describes naming constraints within Amazon Redshift.
Cluster identifier |
|
|
Database name |
|
|
Master user name |
|
|
Master password |
|
|
Parameter group name |
|
|
Cluster security group name |
|
|
Subnet group name |
|
|
Cluster snapshot identifier |
|

