Quotas and constraints for Amazon Aurora

Following, you can find a description of the resource quotas and naming constraints for Amazon Aurora.

Quotas in Amazon Aurora

Each AWS account has quotas, for each AWS Region, on the number of Amazon Aurora resources that can be created. After a quota for a resource has been reached, additional calls to create that resource fail with an exception.

The following table lists the resources and their quotas per AWS Region.

Name	Default	Adjustable
Authorizations per DB security group	All supported Regions: 20	No
Custom engine versions	All supported Regions: 40	Yes
DB cluster parameter groups	All supported Regions: 50	No
DB clusters	All supported Regions: 40	Yes
DB instances	All supported Regions: 40	Yes
DB subnet groups	All supported Regions: 50	Yes
Data API HTTP request body size	All supported Regions: 4 Megabytes	No
Data API maximum concurrent cluster-secret pairs	All supported Regions: 30	No
Data API maximum concurrent requests	All supported Regions: 500	No
Data API maximum result set size	All supported Regions: 1 Megabytes	No
Data API requests per second	All supported Regions: 1,000 per second	No
Event subscriptions	All supported Regions: 20	Yes
IAM roles per DB cluster	All supported Regions: 5	Yes
IAM roles per DB instance	All supported Regions: 5	Yes
Manual DB cluster snapshots	All supported Regions: 100	Yes
Manual DB instance snapshots	All supported Regions: 100	Yes
Option groups	All supported Regions: 20	Yes
Parameter groups	All supported Regions: 50	Yes
Proxies	All supported Regions: 20	Yes
Read replicas per master	All supported Regions: 5	Yes
Reserved DB instances	All supported Regions: 40	Yes
Rules per security group	All supported Regions: 20	No
Security groups	All supported Regions: 25	Yes
Security groups (VPC)	All supported Regions: 5	No
Subnets per DB subnet group	All supported Regions: 20	No
Tags per resource	All supported Regions: 50	No
Total storage for all DB instances	All supported Regions: 100,000 Gigabytes	Yes

Note

By default, you can have up to a total of 40 DB instances. RDS DB instances, Aurora DB instances, Amazon Neptune instances, and Amazon DocumentDB instances apply to this quota.

If your application requires more DB instances, you can request additional DB instances by opening the Service Quotas console. In the navigation pane, choose AWS services. Choose Amazon Relational Database Service (Amazon RDS), choose a quota, and follow the directions to request a quota increase. For more information, see Requesting a quota increase in the Service Quotas User Guide.

Backups managed by AWS Backup are considered manual DB cluster snapshots, but don't count toward the manual cluster snapshot quota. For information about AWS Backup, see the AWS Backup Developer Guide.

If you use any of the Amazon RDS APIs and exceed the default quota for the number of calls per second, the Amazon RDS API issues an error similar to the following: ClientError: An error occurred (ThrottlingException) when calling the API_name operation: Rate exceeded. Reduce the number of calls per second. The quota is meant to cover most use cases. If higher limits are needed, request a quota increase by contacting AWS Support. Open the AWS Support Center page, sign in if necessary, and choose Create case. Choose Service limit increase. Complete and submit the form.

Note

This quota can't be changed in the Amazon RDS Service Quotas console.

Naming constraints in Amazon Aurora

The following table describes naming constraints in Amazon Aurora.

Resource or item	Constraints
DB cluster identifier	Identifiers have these naming constraints: Must contain 1–63 alphanumeric characters or hyphens. First character must be a letter. Can't end with a hyphen or contain two consecutive hyphens. Must be unique for all DB instances per AWS account, per AWS Region.
Initial database name	Database name constraints differ between Aurora MySQL and PostgreSQL. For more information, see the available settings when creating each DB cluster.
Master user name	Master user name constraints differ for each database engine. For more information, see the available settings when creating each DB cluster.
Master password	The password for the database master user can include any printable ASCII character except /, ", @, or a space. Master password length constraints differ for each database engine. For more information, see the available settings when creating each DB cluster.
DB parameter group name	These names have these constraints: Must contain 1–255 alphanumeric characters. First character must be a letter. Hyphens are allowed, but the name cannot end with a hyphen or contain two consecutive hyphens.
DB subnet group name	These names have these constraints: Must contain 1–255 characters. Alphanumeric characters, spaces, hyphens, underscores, and periods are allowed.

Amazon Aurora size limits

Storage size limits

An Aurora cluster volume can grow to a maximum size of 128 tebibytes (TiB) for the following engine versions:

• Aurora MySQL versions 2.09 compatible with MySQL 5.7 and 1.23 compatible with MySQL 5.6

• All Aurora PostgreSQL 13 versions, Aurora PostgreSQL versions 12.4 and higher, 11.7 and higher, 10.12 and higher, and 9.6.17 and higher

For lower engine versions, the maximum size of an Aurora cluster volume is 64 TiB. For more information, see How Aurora storage automatically resizes.

SQL table size limits

For Aurora MySQL, the maximum table size is 64 tebibytes (TiB). For an Aurora PostgreSQL DB cluster, the maximum table size is 32 tebibytes (TiB). We recommend that you follow table design best practices, such as partitioning of large tables.