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.
Resource | Default quota |
---|---|
Authorizations per DB security group | 20 |
Concurrent DB snapshot export tasks | 5 |
Cross-Region DB snapshot copy requests | 5 |
Custom endpoints per DB cluster | 5 |
Data API maximum result set size | 1 MB |
Data API requests per second | 1000 |
DB clusters | 40 |
DB cluster parameter groups | 50 |
DB instances | 40 |
DB subnet groups | 50 |
Event subscriptions | 20 |
AWS Identity and Access Management (IAM) roles per DB cluster | 5 |
IAM roles per DB instance | 5 |
Manual DB cluster snapshots | 100 |
Parameter groups | 50 |
Proxies | 20 |
Reserved DB instances | 40 |
Rules per virtual private cloud (VPC) security group | 50 inbound, 50 outbound |
Subnets per subnet group | 20 |
Tags per resource | 50 |
VPC security groups | 5 |
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
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.
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:
|
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 |
DB parameter group name |
These names have these constraints:
|
DB subnet group name |
These names have these constraints:
|
Amazon Aurora 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.