Quotas and constraints for Amazon Aurora - Amazon Aurora
Quotas in Amazon AuroraNaming constraints in Amazon AuroraAmazon Aurora size limits

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 Description
Authorizations per DB security group Each supported Region: 20 No Number of security group authorizations per DB security group
Custom engine versions Each supported Region: 40 Yes The maximum number of custom engine versions allowed in this account in the current Region
DB cluster parameter groups Each supported Region: 50 No The maximum number of DB cluster parameter groups
DB clusters Each supported Region: 40 Yes The maximum number of Aurora clusters allowed in this account in the current Region
DB instances Each supported Region: 40 Yes The maximum number of DB instances allowed in this account in the current Region
DB shard groups Each supported Region: 5 Yes The maximum number of DB shard groups for Aurora Limitless Database in this account in the current Region
DB subnet groups Each supported Region: 50 Yes The maximum number of DB subnet groups
Data API HTTP request body size Each supported Region: 4 Megabytes No The maximum size allowed for the HTTP request body.
Data API maximum concurrent cluster-secret pairs Each supported Region: 30 No The maximum number of unique pairs of Aurora Serverless v1 DB clusters and secrets in concurrent Data API requests for this account in the current AWS Region.
Data API maximum concurrent requests Each supported Region: 500 No The maximum number of Data API requests to an Aurora Serverless v1 DB cluster that use the same secret and can be processed at the same time. Additional requests are queued and processed as in-process requests complete.
Data API maximum result set size Each supported Region: 1 Megabytes No The maximum size of the database result set that can be returned by the Data API.
Data API maximum size of JSON response string Each supported Region: 10 Megabytes No The maximum size of the simplified JSON response string returned by the RDS Data API.
Data API requests per second Each supported Region: 1,000 per second No The maximum number of requests to the Data API per second allowed in this account in the current AWS Region
Event subscriptions Each supported Region: 20 Yes The maximum number of event subscriptions
IAM roles per DB cluster Each supported Region: 5 Yes The maximum number of IAM roles associated with a DB cluster
IAM roles per DB instance Each supported Region: 5 Yes The maximum number of IAM roles associated with a DB instance
Integrations Each supported Region: 100 No The maximum number of integrations allowed in this account in the current AWS Region
Manual DB cluster snapshots Each supported Region: 100 Yes The maximum number of manual DB cluster snapshots
Manual DB instance snapshots Each supported Region: 100 Yes The maximum number of manual DB instance snapshots
Option groups Each supported Region: 20 Yes The maximum number of option groups
Parameter groups Each supported Region: 50 Yes The maximum number of parameter groups
Proxies Each supported Region: 20 Yes The maximum number of proxies allowed in this account in the current AWS Region
Read replicas per primary Each supported Region: 15 Yes The maximum number of read replicas per primary DB instance. This quota cant be adjusted for Amazon Aurora.
Reserved DB instances Each supported Region: 40 Yes The maximum number of reserved DB instances allowed in this account in the current AWS Region
Rules per security group Each supported Region: 20 No The maximum number of rules per DB security group
Security groups Each supported Region: 25 Yes The maximum number of DB security groups
Security groups (VPC) Each supported Region: 5 No The maximum number of DB security groups per Amazon VPC
Subnets per DB subnet group Each supported Region: 20 No The maximum number of subnets per DB subnet group
Tags per resource Each supported Region: 50 No The maximum number of tags per Amazon RDS resource
Total storage for all DB instances Each supported Region: 100,000 Gigabytes Yes The maximum total storage (in GB) on EBS volumes for all Amazon RDS DB instances added together. This quota does not apply to Amazon Aurora, which has a maximum cluster volume of 128 TiB for each DB cluster.
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 clustersnapshots, 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 RDS API operations and exceed the default quota for the number of calls per second, the Amazon RDS API issues an error like the following one.

ClientError: An error occurred (ThrottlingException) when calling the API_name operation: Rate exceeded.

Here, reduce the number of calls per second. The quota is meant to cover most use cases. If higher quotas are needed, you can request a quota increase by using one of the following options:

For more information, see the Service Quotas User Guide.

Naming constraints in Amazon Aurora

The naming constraints in Amazon Aurora are as follows:

  • DB cluster identifier:

    • 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 Aurora PostgreSQL. For more information, see the available settings when creating each DB cluster.

  • Master username – Master username constraints differ for each database engine. For more information, see the available settings when creating the DB cluster.

  • Master password:

    • The password for the database master user can include any printable ASCII character except /, ', ", @, or a space.

    • The password can contain the following number of printable ASCII characters depending on the DB engine:

      • Aurora MySQL: 8–41

      • Aurora PostgreSQL: 8–99

  • DB parameter group:

    • 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:

    • 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:

  • All available Aurora MySQL version 3 versions; Aurora MySQL version 2, versions 2.09 and higher

  • All available Aurora PostgreSQL versions

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

To monitor the remaining storage space, you can use the AuroraVolumeBytesLeftTotal metric. For more information, see Cluster-level metrics for Amazon Aurora.

SQL table size limits

For an Aurora MySQL DB cluster, 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.

Table space ID limits

The maximum table space ID for Aurora MySQL is 2147483647. If you frequently create and drop tables, make sure to be aware of your table space IDs and plan to use logical dumps. For more information, see Logical migration from MySQL to Amazon Aurora MySQL by using mysqldump.