RDS instances on RDS Basic Edition (with cloud disks)
RDS edition | Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections (default value) | Storage | ||
Maximum IOPS | Maximum I/O bandwidth supported by the instance type (MB/s) | Storage capacity | |||||
RDS Basic Edition | General-purpose instance family | mysql.n2.medium.1 | 2 cores, 4 GB | 4,000 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your workloads are sensitive to IOPS, we recommend that you use RDS High-availability Edition and dedicated instance types. |
| |
mysql.n4.medium.1 | 2 cores, 8 GB | 6,000 | |||||
mysql.n2.large.1 | 4 cores, 8 GB | 6,000 | |||||
mysql.n4.large.1 | 4 cores, 16 GB | 8,000 | |||||
mysql.n2.xlarge.1 | 8 cores, 16 GB | 8,000 | |||||
mysql.n4.xlarge.1 | 8 cores, 32 GB | 10,000 | |||||
RDS instances on RDS High-availability Edition (with cloud disks)
Formulas to calculate the maximum I/O bandwidth of a cloud disk:
General ESSDs:
ESSDs:
PL1 ESSD:
min{120 + 0.5 × Storage capacity, 350, Maximum I/O bandwidth supported by the instance type}PL2 ESSD:
min{120 + 0.5 × Storage capacity, 750, Maximum I/O bandwidth supported by the instance type}PL3 ESSD:
min{120 + 0.5 × Storage capacity, 4000, Maximum I/O bandwidth supported by the instance type}
RDS edition | Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections (default value) | Storage | ||
Maximum IOPS | Maximum I/O bandwidth supported by the instance type (MB/s) | Storage capacity | |||||
RDS High-availability Edition | General-purpose instance family | mysql.n2.small.2c | 1 core, 2 GB | 2,000 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your workloads are sensitive to IOPS, we recommend that you use dedicated instance types. |
Note ApsaraDB RDS for MySQL supports automatic storage expansion when the storage usage of an RDS instance reaches the threshold that you specify. For more information, see Configure automatic storage expansion. | |
mysql.n2.medium.2c | 2 cores, 4 GB | 4,000 | |||||
Dedicated instance family | mysql.x2.medium.2c | 2 cores, 4 GB | 4,000 | 10,000 | 128 | ||
mysql.x2.large.2c | 4 cores, 8 GB | 6,000 | 20,000 | 192 | |||
mysql.x2.xlarge.2c | 8 cores, 16 GB | 8,000 | 25,000 | 256 | |||
mysql.x2.3large.2c | 12 cores, 24 GB | 12,000 | 30,000 | 320 | |||
mysql.x2.2xlarge.2c | 16 cores, 32 GB | 16,000 | 40,000 | 384 | |||
mysql.x2.3xlarge.2c | 24 cores, 48 GB | 24,000 | 50,000 | 512 | |||
mysql.x2.4xlarge.2c | 32 cores, 64 GB | 32,000 | 60,000 | 640 | |||
mysql.x2.13large.2c | 52 cores, 96 GB | 52,000 | 100,000 | 1,024 | |||
mysql.x2.8xlarge.2c | 64 cores, 128 GB | 64,000 | 120,000 | 1,280 | |||
mysql.x2.13xlarge.2c | 104 cores, 192 GB | 104,000 | 200,000 | 2,048 | |||
mysql.x4.medium.2c | 2 cores, 8 GB | 6,000 | 10,000 | 128 | |||
mysql.x4.large.2c | 4 cores, 16 GB | 8,000 | 20,000 | 192 | |||
mysql.x4.xlarge.2c | 8 cores, 32 GB | 10,000 | 25,000 | 256 | |||
mysql.x4.3large.2c | 12 cores, 48 GB | 15,000 | 30,000 | 320 | |||
mysql.x4.2xlarge.2c | 16 cores, 64 GB | 20,000 | 40,000 | 384 | |||
mysql.x4.3xlarge.2c | 24 cores, 96 GB | 30,000 | 50,000 | 512 | |||
mysql.x4.4xlarge.2c | 32 cores, 128 GB | 40,000 | 60,000 | 640 | |||
mysql.x4.13large.2c | 52 cores, 192 GB | 65,000 | 100,000 | 1,024 | |||
mysql.x4.8xlarge.2c | 64 cores, 256 GB | 80,000 | 120,000 | 1,280 | |||
mysql.x4.13xlarge.2c | 104 cores, 384 GB | 130,000 | 200,000 | 2,048 | |||
mysql.x8.medium.2c | 2 cores, 16 GB | 8,000 | 10,000 | 128 | |||
mysql.x8.large.2c | 4 cores, 32 GB | 12,000 | 20,000 | 192 | |||
mysql.x8.xlarge.2c | 8 cores, 64 GB | 16,000 | 25,000 | 256 | |||
mysql.x8.3large.2c | 12 cores, 96 GB | 24,000 | 30,000 | 320 | |||
mysql.x8.2xlarge.2c | 16 cores, 128 GB | 32,000 | 40,000 | 384 | |||
mysql.x8.3xlarge.2c | 24 cores, 192 GB | 48,000 | 50,000 | 512 | |||
mysql.x8.4xlarge.2c | 32 cores, 256 GB | 64,000 | 60,000 | 640 | |||
mysql.x8.13large.2c | 52 cores, 384 GB | 104,000 | 100,000 | 1,024 | |||
mysql.x8.8xlarge.2c | 64 cores, 512 GB | 128,000 | 120,000 | 1,280 | |||
mysql.x8.13xlarge.2c | 104 cores, 768 GB | 208,000 | 200,000 | 2,048 | |||
RDS instances on RDS High-availability Edition (with local disks)
Starting November 29, 2024, the maximum IOPS of an ApsaraDB RDS for MySQL instance that uses local disks is increased to 150,000. For more information, see [Product changes/Feature changes] The maximum IOPS of ApsaraDB RDS for MySQL instances with local disks is increased.
RDS edition | Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections (default value) | Storage | |
Maximum IOPS | Storage capacity | |||||
RDS High-availability Edition | General-purpose | rds.mysql.t1.small | 1 core, 1 GB | 300 | 1,200 | 5 GB to 2,000 GB |
rds.mysql.s1.small | 1 core, 2 GB | 600 | 2,000 | |||
rds.mysql.s2.large | 2 cores, 4 GB | 1,200 | 4,000 | |||
rds.mysql.s2.xlarge | 2 cores, 8 GB | 2,000 | 6,000 | |||
rds.mysql.s3.large | 4 cores, 8 GB | 2,000 | 8,000 | |||
rds.mysql.m1.medium | 4 cores, 16 GB | 4,000 | 14,000 | |||
rds.mysql.c1.large | 8 cores, 16 GB | 4,000 | 20,000 | |||
rds.mysql.c1.xlarge | 8 cores, 32 GB | 8,000 | 28,000 | |||
rds.mysql.c2.xlarge | 16 cores, 64 GB | 16,000 | 40,000 | 5 GB to 3,000 GB | ||
rds.mysql.c2.xlp2 | 16 cores, 96 GB | 24,000 | 40,000 | |||
Dedicated instance type | mysql.x4.large.2 | 4 cores, 16 GB | 2,500 | 30,000 | 20 GB to 2,000 GB | |
mysql.x4.xlarge.2 | 8 cores, 32 GB | 5,000 | 45,000 | 500 GB to 3,000 GB | ||
mysql.x4.2xlarge.2 | 16 cores, 64 GB | 10,000 | 60,000 | |||
mysql.x4.4xlarge.2 | 32 cores, 128 GB | 20,000 | 80,000 | 1,000 GB to 8,000 GB | ||
mysql.x4.8xlarge.2 | 64 cores, 256 GB | 40,000 | 150,000 | |||
mysql.x8.medium.2 | 2 cores, 16 GB | 2,500 | 15,000 | 20 GB to 2,000 GB | ||
mysql.x8.large.2 | 4 cores, 32 GB | 5,000 | 40,000 | |||
mysql.x8.xlarge.2 | 8 cores, 64 GB | 10,000 | 50,000 | 500 GB to 3,000 GB | ||
mysql.x8.2xlarge.2 | 16 cores, 128 GB | 20,000 | 60,000 | |||
mysql.x8.4xlarge.2 | 32 cores, 256 GB | 40,000 | 100,000 | 1,000 GB to 8,000 GB | ||
mysql.x8.8xlarge.2 | 64 cores, 512 GB | 80,000 | 150,000 | |||
Dedicated host | rds.mysql.st.h43 | 60 cores, 470 GB | 100,000 | 150,000 | 3,000 GB to 8,000 GB | |
rds.mysql.st.v52 | 90 cores, 720 GB | 150,000 | 150,000 | 1,000 GB to 8,000 GB | ||
If your RDS instance uses one of the following instance types and the pay-as-you-go billing method, the maximum storage capacity that is allowed for your RDS instance is increased from 2,000 GB to 3,000 GB in emergency situations.
mysql.x8.medium.2
mysql.x4.large.2
mysql.x8.large.2
If your RDS instance uses one of the preceding instance types and the used storage exceeds 2,000 GB, you cannot change the billing method from pay-as-you-go to subscription. You can change the billing method only when the used storage is less than 2,000 GB.
RDS instances on RDS Enterprise Edition (with local disks)
RDS Enterprise Edition for ApsaraDB RDS for MySQL is no longer available for purchase from March 27, 2023. If you want to continue to use RDS Enterprise Edition for ApsaraDB RDS for MySQL, take note of the following items:
If you do not have an existing RDS instance that runs RDS Enterprise Edition, we recommend that you purchase an RDS instance that runs RDS Cluster Edition or PolarDB-X 2.0 Standard Edition instance instead.
If you have an existing RDS instance that runs RDS Enterprise Edition, we recommend that you migrate the data of the RDS instance to an RDS instance that runs RDS Cluster Edition or a PolarDB-X 2.0 Standard Edition instance. For more information, see [Product changes/Feature changes] Extended support for RDS Enterprise Edition for ApsaraDB RDS for MySQL
RDS edition | Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Storage | |
Maximum IOPS | Storage capacity | |||||
RDS Enterprise Edition | General-purpose instance family | MySQL 5.7 and MySQL 8.0: mysql.n2.small.25 | 1 core, 2 GB | 600 | 1,000 | 5 GB to 2,000 GB |
MySQL 5.7 and MySQL 8.0: mysql.n2.medium.25 | 2 cores, 4 GB | 1,200 | 2,000 | 5 GB to 2,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.n4.medium.25 | 2 cores, 8 GB | 2,000 | 4,000 | 5 GB to 2,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.n2.large.25 | 4 cores, 8 GB | 2,000 | 5,000 | 5 GB to 2,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.n4.large.25 | 4 cores, 16 GB | 4,000 | 7,000 | 5 GB to 2,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.n2.xlarge.25 | 8 cores, 16 GB | 4,000 | 8,000 | 5 GB to 2,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.n4.xlarge.25 | 8 cores, 32 GB | 8,000 | 12,000 | 5 GB to 2,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.n4.2xlarge.25 | 16 cores, 64 GB | 16,000 | 14,000 | 5 GB to 3,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.n8.2xlarge.25 | 16 cores, 128 GB | 32,000 | 16,000 | 5 GB to 3,000 GB | ||
Dedicated (with a large number of CPU cores) | MySQL 5.7 and MySQL 8.0: mysql.x4.large.25 | 4 cores, 16 GB | 2,500 | 4,500 | 50 GB to 2,000 GB | |
MySQL 5.7 and MySQL 8.0: mysql.x4.xlarge.25 | 8 cores, 32 GB | 5,000 | 9,000 | 500 GB to 3,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.x4.2xlarge.25 | 16 cores, 64 GB | 10,000 | 18,000 | 500 GB to 3,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.x4.4xlarge.25 | 32 cores, 128 GB | 20,000 | 36,000 | 1,000 GB to 6,000 GB | ||
Dedicated (with a large memory capacity) | MySQL 5.7 and MySQL 8.0: mysql.x8.medium.25 | 2 cores, 16 GB | 2,500 | 4,500 | 50 GB to 2,000 GB | |
MySQL 5.7 and MySQL 8.0: mysql.x8.large.25 | 4 cores, 32 GB | 5,000 | 9,000 | 50 GB to 2,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.x8.xlarge.25 | 8 cores, 64 GB | 10,000 | 18,000 | 500 GB to 3,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.x8.2xlarge.25 | 16 cores, 128 GB | 20,000 | 36,000 | 500 GB to 3,000 GB | ||
MySQL 5.7 and MySQL 8.0: mysql.x8.4xlarge.25 | 32 cores, 256 GB | 40,000 | 72,000 | 1,000 GB to 6,000 GB | ||
Dedicated host instance family | MySQL 5.7 and MySQL 8.0: mysql.st.8xlarge.25 | 60 cores, 470 GB | 100,000 | 120,000 | 3,000 GB, 4,000 GB, 5,000 GB, or 6,000 GB | |
MySQL 5.7 and MySQL 8.0: mysql.st.12xlarge.25 | 90 cores, 720 GB | 150,000 | 140000 | 1,000 GB to 6,000 GB | ||
If your RDS instance uses one of the following instance types and the pay-as-you-go billing method, the maximum storage capacity that is allowed for your RDS instance is increased to 3,000 GB in emergency situations.
mysql.x8.medium.25
mysql.x4.large.25
mysql.x8.large.25
Note: If your RDS instance uses one of the preceding instance types and the used storage exceeds 2,000 GB, you cannot change the billing method from pay-as-you-go to subscription. You can change the billing method only when the used storage is less than 2,000 GB.
RDS clusters (with cloud disks)
An ApsaraDB RDS for MySQL cluster supports MySQL 5.7 and MySQL 8.0.
RDS Cluster Edition for ApsaraDB RDS for MySQL is available for purchase in some regions. The following table describes the regions where RDS Cluster Edition for ApsaraDB RDS for MySQL is supported and the estimated release date in other regions. The actual release date prevails.
Formulas to calculate the maximum I/O bandwidth of a cloud disk:
General ESSDs:
ESSDs:
PL1 ESSD:
min{120 + 0.5 × Storage capacity, 350, Maximum I/O bandwidth supported by the instance type}PL2 ESSD:
min{120 + 0.5 × Storage capacity, 750, Maximum I/O bandwidth supported by the instance type}PL3 ESSD:
min{120 + 0.5 × Storage capacity, 4000, Maximum I/O bandwidth supported by the instance type}
RDS edition | Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections (default value) | Storage | ||
Maximum IOPS | Maximum I/O bandwidth supported by the instance type (MB/s) | Storage capacity | |||||
RDS Cluster Edition | General-purpose instance family | mysql.n2.medium.xc | 2 cores, 4 GB | 4,000 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed for RDS instances that use general-purpose instance types. If your workloads are sensitive to IOPS, we recommend that you use dedicated instance types. |
Note ApsaraDB RDS for MySQL supports automatic storage expansion when the storage usage of an RDS instance reaches the threshold that you specify. For more information, see Configure automatic storage expansion. | |
mysql.n4.medium.xc | 2 cores, 8 GB | 6,000 | |||||
mysql.n8.medium.xc | 2 cores, 16 GB | 8,000 | |||||
mysql.n2.large.xc | 4 cores, 8 GB | 6,000 | |||||
mysql.n4.large.xc | 4 cores, 16 GB | 8,000 | |||||
mysql.n8.large.xc | 4 cores, 32 GB | 12,000 | |||||
mysql.n2.xlarge.xc | 8 cores, 16 GB | 12,000 | |||||
mysql.n4.xlarge.xc | 8 cores, 32 GB | 12,000 | |||||
mysql.n8.xlarge.xc | 8 cores, 64 GB | 16,000 | |||||
Dedicated instance family | mysql.x2.medium.xc | 2 cores, 4 GB | 4,000 | 10,000 | 128 | ||
mysql.x4.medium.xc | 2 cores, 8 GB | 6,000 | 10,000 | 128 | |||
mysql.x8.medium.xc | 2 cores, 16 GB | 8,000 | 10,000 | 128 | |||
mysql.x2.large.xc | 4 cores, 8 GB | 6,000 | 20,000 | 192 | |||
mysql.x4.large.xc | 4 cores, 16 GB | 8,000 | 20,000 | 192 | |||
mysql.x8.large.xc | 4 cores, 32 GB | 12,000 | 20,000 | 192 | |||
mysql.x2.xlarge.xc | 8 cores, 16 GB | 12,000 | 25,000 | 256 | |||
mysql.x4.xlarge.xc | 8 cores, 32 GB | 12,000 | 25,000 | 256 | |||
mysql.x8.xlarge.xc | 8 cores, 64 GB | 16,000 | 25,000 | 256 | |||
mysql.x2.3large.xc | 12 cores, 24 GB | 12,000 | 30,000 | 320 | |||
mysql.x4.3large.xc | 12 cores, 48 GB | 15,000 | 30,000 | 320 | |||
mysql.x8.3large.xc | 12 cores, 96 GB | 24,000 | 30,000 | 320 | |||
mysql.x2.2xlarge.xc | 16 cores, 32 GB | 16,000 | 40,000 | 384 | |||
mysql.x4.2xlarge.xc | 16 cores, 64 GB | 20,000 | 40,000 | 384 | |||
mysql.x8.2xlarge.xc | 16 cores, 128 GB | 32,000 | 40,000 | 384 | |||
mysql.x2.3xlarge.xc | 24 cores, 48 GB | 24,000 | 50,000 | 512 | |||
mysql.x4.3xlarge.xc | 24 cores, 96 GB | 30,000 | 50,000 | 512 | |||
mysql.x8.3xlarge.xc | 24 cores, 192 GB | 48,000 | 50,000 | 512 | |||
mysql.x2.4xlarge.xc | 32 cores, 64 GB | 32,000 | 60,000 | 640 | |||
mysql.x4.4xlarge.xc | 32 cores, 128 GB | 40,000 | 60,000 | 640 | |||
mysql.x8.4xlarge.xc | 32 cores, 256 GB | 64,000 | 60,000 | 640 | |||
mysql.x2.13large.xc | 52 cores, 96 GB | 52,000 | 100,000 | 1,024 | |||
mysql.x4.13large.xc | 52 cores, 192 GB | 65,000 | 100,000 | 1,024 | |||
mysql.x8.13large.xc | 52 cores, 384 GB | 104,000 | 100,000 | 1,024 | |||
mysql.x2.8xlarge.xc | 64 cores, 128 GB | 64,000 | 120,000 | 1,280 | |||
mysql.x4.8xlarge.xc | 64 cores, 256 GB | 80,000 | 120,000 | 1,280 | |||
mysql.x8.8xlarge.xc | 64 cores, 512 GB | 128,000 | 120,000 | 1,280 | |||
mysql.x2.13xlarge.xc | 104 cores, 192 GB | 104,000 | 200,000 | 2,048 | |||
mysql.x4.13xlarge.xc | 104 cores, 384 GB | 130,000 | 200,000 | 2,048 | |||
mysql.x8.13xlarge.xc | 104 cores, 768 GB | 208,000 | 200,000 | 2,048 | |||