This topic describes the latest and legacy instance types for primary instances of the standard edition (formerly x86) of ApsaraDB RDS for MySQL.
-
For DuckDB Analytics instance types, see DuckDB Analytics Primary Instance Types and DuckDB Analytics Read-only Instance Types.
-
To learn about the differences between the Yitian edition and the standard edition, see Product types.
-
This list may include discontinued instance types. For currently available instance types, see the buy page.
-
RDS for MySQL Serverless instances use RCUs as the resource measurement unit and do not have conventional CPU and memory specifications. For compatibility, they use the instance type codes
mysql.n2.serverless.1c(Basic Edition) andmysql.n2.serverless.2c(High-availability Edition). -
SSD cloud disks are no longer available for purchase for some RDS instances. You can purchase higher-performance ESSD cloud disks instead. For more information, see [EOS/Discontinuation] End of sale for the SSD cloud disk for specific database engines in ApsaraDB RDS from July 01, 2022.
-
The maximum number of connections in the instance type list is the maximum number of concurrent connections to an RDS for MySQL instance.
-
If you cannot select a specific instance type when performing an instance type change, it may be because supported instance types vary by region. The instance types available on the buy page take precedence.
-
You cannot adjust the public bandwidth of an ApsaraDB RDS for MySQL instance.
RDS Basic Edition instances with cloud disks
-
Actual maximum IOPS: The actual maximum IOPS depends on the storage type, storage capacity, and instance type. For more information, see Maximum IOPS.
-
Actual maximum I/O bandwidth: The actual maximum I/O bandwidth depends on the storage type, storage capacity, and instance type. For more information, see Maximum throughput.
|
RDS edition |
Instance family |
Instance type |
CPU and memory |
Maximum connections (default value) |
Storage |
||
|
Maximum IOPS |
Maximum I/O bandwidth (Mbit/s) |
Storage capacity |
|||||
|
RDS Basic Edition |
General-purpose |
mysql.n2.medium.1 |
2 cores, 4 GB |
4000 |
General-purpose instance types do not guarantee maximum IOPS or maximum I/O bandwidth. If your business is sensitive to IOPS, select a dedicated instance type of the High-availability Edition |
|
|
|
mysql.n4.medium.1 |
2 cores, 8 GB |
6000 |
|||||
|
mysql.n2.large.1 |
4 cores, 8 GB |
6000 |
|||||
|
mysql.n4.large.1 |
4 cores, 16 GB |
8000 |
|||||
|
mysql.n2.xlarge.1 |
8 cores, 16 GB |
8000 |
|||||
|
mysql.n4.xlarge.1 |
8 cores, 32 GB |
10000 |
|||||
RDS High-availability Edition instances with cloud disks
-
Actual maximum IOPS: The actual maximum IOPS depends on the storage type, storage capacity, and instance type. For more information, see Maximum IOPS.
-
Actual maximum I/O bandwidth: The actual maximum I/O bandwidth depends on the storage type, storage capacity, and instance type. For more information, see Maximum throughput.
|
RDS edition |
Instance family |
Instance type |
CPU and memory |
Maximum connections (default value) |
Storage |
||
|
Maximum IOPS |
Maximum I/O bandwidth (Mbit/s) |
Storage capacity |
|||||
|
RDS High-availability Edition |
General-purpose |
mysql.n2.small.2c |
1 core, 2 GB |
2,000 |
General-purpose instance types do not guarantee maximum IOPS or maximum I/O bandwidth. If your business is sensitive to IOPS, select a dedicated instance type. |
Note
RDS for MySQL supports automatic storage scaling when the storage usage reaches a specified threshold. For more information, see Automatic storage and performance scaling. |
|
|
mysql.n2.medium.2c |
2 cores, 4 GB |
4,000 |
|||||
|
Dedicated |
mysql.x2.medium.2c |
2 cores, 4 GB |
4,000 |
10,000 |
125 |
||
|
mysql.x4.medium.2c |
2 cores, 4 GB |
6,000 |
|||||
|
mysql.x8.medium.2c |
2 cores, 16 GB |
8,000 |
|||||
|
mysql.x2.large.2c |
4 cores, 8 GB |
6,000 |
20,000 |
187.5 |
|||
|
mysql.x4.large.2c |
4 cores, 16 GB |
8,000 |
|||||
|
mysql.x8.large.2c |
4 cores, 32 GB |
12,000 |
|||||
|
mysql.x2.xlarge.2c |
8 cores, 16 GB |
8,000 |
25,000 |
250 |
|||
|
mysql.x4.xlarge.2c |
8 cores, 32 GB |
10,000 |
|||||
|
mysql.x8.xlarge.2c |
8 cores, 64 GB |
16,000 |
|||||
|
mysql.x2.3large.2c |
12 cores, 24 GB |
12,000 |
30,000 |
312.5 |
|||
|
mysql.x4.3large.2c |
12 cores, 48 GB |
15,000 |
|||||
|
mysql.x8.3large.2c |
12 cores, 96 GB |
24,000 |
|||||
|
mysql.x2.2xlarge.2c |
16 cores, 32 GB |
16,000 |
40,000 |
375 |
|||
|
mysql.x4.2xlarge.2c |
16 cores, 64 GB |
20,000 |
|||||
|
mysql.x8.2xlarge.2c |
16 cores, 128 GB |
32,000 |
|||||
|
mysql.x2.3xlarge.2c |
24 cores, 48 GB |
24,000 |
50,000 |
500 |
|||
|
mysql.x4.3xlarge.2c |
24 cores, 96 GB |
30,000 |
|||||
|
mysql.x8.3xlarge.2c |
24 cores, 192 GB |
48,000 |
|||||
|
mysql.x2.4xlarge.2c |
32 cores, 64 GB |
32,000 |
60,000 |
625 |
|||
|
mysql.x4.4xlarge.2c |
32 cores, 128 GB |
40,000 |
|||||
|
mysql.x8.4xlarge.2c |
32 cores, 256 GB |
64,000 |
|||||
|
mysql.x2.13large.2c |
52 cores, 96 GB |
52,000 |
100,000 |
1,000 |
|||
|
mysql.x4.13large.2c |
52 cores, 192 GB |
65,000 |
|||||
|
mysql.x8.13large.2c |
52 cores, 384 GB |
104,000 |
|||||
|
mysql.x2.8xlarge.2c |
64 cores, 128 GB |
64,000 |
120,000 |
1,025 |
|||
|
mysql.x4.8xlarge.2c |
64 cores, 256 GB |
80,000 |
150,000 |
||||
|
mysql.x8.8xlarge.2c |
64 cores, 512 GB |
128,000 |
150,000 |
||||
|
mysql.x2.13xlarge.2c |
104 cores, 192 GB |
104,000 |
200,000 |
2,000 |
|||
|
mysql.x4.13xlarge.2c |
104 cores, 384 GB |
130,000 |
200,000 |
2,000 |
|||
|
mysql.x8.13xlarge.2c |
104 cores, 768 GB |
208,000 |
200,000 |
2,000 |
|||
|
mysql.x4.16xlarge.2c |
128 cores, 512 GB |
128,000 |
300,000 |
2,560 |
|||
RDS Cluster Edition instances with cloud disks
RDS for MySQL instances that run RDS Cluster Edition support MySQL 5.7 and MySQL 8.0.
-
RDS MySQL Cluster Edition is available in all regions except for UAE (Dubai), China (Nanjing), and China (Fuzhou). Support for these regions will be added gradually. For the latest availability information, refer to the console.
-
Actual maximum IOPS: The actual maximum IOPS depends on the storage type, storage capacity, and instance type. For more information, see Maximum IOPS.
-
Actual maximum I/O bandwidth: The actual maximum I/O bandwidth depends on the storage type, storage capacity, and instance type. For more information, see Maximum throughput.
|
RDS edition |
Instance family |
Instance type |
CPU and memory |
Maximum connections (default value) |
Storage |
||
|
Maximum IOPS |
Maximum I/O bandwidth (Mbit/s) |
Storage capacity |
|||||
|
RDS Cluster Edition |
General-purpose |
mysql.n2.medium.xc |
2 cores, 4 GB |
4,000 |
General-purpose instance types do not guarantee maximum IOPS or maximum I/O bandwidth. If your business is sensitive to IOPS, select a dedicated instance type. |
Note
RDS for MySQL supports automatic storage scaling when the storage usage reaches a specified threshold. For more information, see Automatic storage and performance scaling. |
|
|
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 |
mysql.x2.medium.xc |
2 cores, 4 GB |
4,000 |
10,000 |
125 |
||
|
mysql.x4.medium.xc |
2 cores, 8 GB |
6,000 |
|||||
|
mysql.x8.medium.xc |
2 cores, 16 GB |
8,000 |
|||||
|
mysql.x2.large.xc |
4 cores, 8 GB |
6,000 |
20,000 |
187.5 |
|||
|
mysql.x4.large.xc |
4 cores, 16 GB |
8,000 |
|||||
|
mysql.x8.large.xc |
4 cores, 32 GB |
12,000 |
|||||
|
mysql.x2.xlarge.xc |
8 cores, 16 GB |
12,000 |
25,000 |
250 |
|||
|
mysql.x4.xlarge.xc |
8 cores, 32 GB |
12,000 |
|||||
|
mysql.x8.xlarge.xc |
8 cores, 64 GB |
16,000 |
|||||
|
mysql.x2.3large.xc |
12 cores, 24 GB |
12,000 |
30,000 |
312.5 |
|||
|
mysql.x4.3large.xc |
12 cores, 48 GB |
15,000 |
|||||
|
mysql.x8.3large.xc |
12 cores, 96 GB |
24,000 |
|||||
|
mysql.x2.2xlarge.xc |
16 cores, 32 GB |
16,000 |
40,000 |
375 |
|||
|
mysql.x4.2xlarge.xc |
16 cores, 64 GB |
20,000 |
|||||
|
mysql.x8.2xlarge.xc |
16 cores, 128 GB |
32,000 |
|||||
|
mysql.x2.3xlarge.xc |
24 cores, 48 GB |
24,000 |
50,000 |
500 |
|||
|
mysql.x4.3xlarge.xc |
24 cores, 96 GB |
30,000 |
|||||
|
mysql.x8.3xlarge.xc |
24 cores, 192 GB |
48,000 |
|||||
|
mysql.x2.4xlarge.xc |
32 cores, 64 GB |
32,000 |
60,000 |
625 |
|||
|
mysql.x4.4xlarge.xc |
32 cores, 128 GB |
40,000 |
|||||
|
mysql.x8.4xlarge.xc |
32 cores, 256 GB |
64,000 |
|||||
|
mysql.x2.13large.xc |
52 cores, 96 GB |
52,000 |
100,000 |
1,000 |
|||
|
mysql.x4.13large.xc |
52 cores, 192 GB |
65,000 |
|||||
|
mysql.x8.13large.xc |
52 cores, 384 GB |
104,000 |
|||||
|
mysql.x2.8xlarge.xc |
64 cores, 128 GB |
64,000 |
120,000 |
1,025 |
|||
|
mysql.x4.8xlarge.xc |
64 cores, 256 GB |
80,000 |
150,000 |
1,025 |
|||
|
mysql.x8.8xlarge.xc |
64 cores, 512 GB |
128,000 |
150,000 |
1,000 |
|||
|
mysql.x2.13xlarge.xc |
104 cores, 192 GB |
104,000 |
200,000 |
2,000 |
|||
|
mysql.x4.13xlarge.xc |
104 cores, 384 GB |
130,000 |
|||||
|
mysql.x8.13xlarge.xc |
104 cores, 768 GB |
208,000 |
|||||
RDS High-availability Edition instances with Premium Local SSDs
Starting from 00:00 (Singapore time) on September 19, 2025, the default maximum number of connections and maximum IOPS for some dedicated RDS for MySQL instance types that use Premium Local SSDs are increased. For more information, see [Product/Feature Change] Increased Default Maximum Connections and Maximum IOPS for RDS for MySQL Instances with Premium Local SSDs.
|
RDS edition |
Instance family |
Instance type |
CPU and memory |
Maximum 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 4,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 |
5 GB to 5,000 GB |
||
|
rds.mysql.c1.xlarge |
8 cores, 32 GB |
8,000 |
28,000 |
|||
|
rds.mysql.c2.xlarge |
16 cores, 64 GB |
16,000 |
40,000 |
20 GB to 12,000 GB |
||
|
rds.mysql.c2.xlp2 |
16 cores, 96 GB |
24,000 |
40,000 |
|||
|
Dedicated |
mysql.x2.medium.2 |
2 cores, 4 GB |
4,000 |
15,000 |
20 GB to 4,000 GB |
|
|
mysql.x4.medium.2 |
2 cores, 8 GB |
6,000 |
20,000 |
|||
|
mysql.x6.medium.2 |
2 cores, 12 GB |
7,000 |
25,000 |
|||
|
mysql.x8.medium.2 |
2 cores, 16 GB |
8,000 |
30,000 |
|||
|
mysql.x2.large.2 |
4 cores, 8 GB |
6,000 |
30,000 |
|||
|
mysql.x4.large.2 |
4 cores, 16 GB |
8,000 |
40,000 |
|||
|
mysql.x6.large.2 |
4 cores, 24 GB |
10,000 |
40,000 |
|||
|
mysql.x8.large.2 |
4 cores, 32 GB |
12,000 |
60,000 |
|||
|
mysql.x2.xlarge.2 |
8 cores, 16 GB |
8,000 |
45,000 |
20 GB to 5,000 GB |
||
|
mysql.x4.xlarge.2 |
8 cores, 32 GB |
12,000 |
60,000 |
|||
|
mysql.x6.xlarge.2 |
8 cores, 48 GB |
14,000 |
60,000 |
|||
|
mysql.x8.xlarge.2 |
8 cores, 64 GB |
16,000 |
90,000 |
|||
|
mysql.x2.2xlarge.2 |
16 cores, 32 GB |
12,000 |
60,000 |
20 GB to 12,000 GB |
||
|
mysql.x4.2xlarge.2 |
16 cores, 64 GB |
16,000 |
75,000 |
|||
|
mysql.x6.2xlarge.2 |
16 cores, 96 GB |
24,000 |
75,000 |
|||
|
mysql.x8.2xlarge.2 |
16 cores, 128 GB |
32,000 |
105,000 |
|||
|
mysql.x2.4xlarge.2 |
32 cores, 64 GB |
16,000 |
80,000 |
|
||
|
mysql.x4.4xlarge.2 |
32 cores, 128 GB |
32,000 |
105,000 |
|||
|
mysql.x6.4xlarge.2 |
32 cores, 192 GB |
36,000 |
120,000 |
|||
|
mysql.x8.4xlarge.2 |
32 cores, 256 GB |
40,000 |
135,000 |
|||
|
mysql.x2.8xlarge.2 |
64 cores, 128 GB |
32,000 |
140,000 |
|||
|
mysql.x4.8xlarge.2 |
64 cores, 256 GB |
40,000 |
150,000 |
|||
|
mysql.x6.8xlarge.2 |
64 cores, 384 GB |
60,000 |
150,000 |
|||
|
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 |
20 GB to 12,000 GB |
|
|
rds.mysql.st.v52 |
90 cores, 720 GB |
150,000 |
150,000 |
|||
Phased-out ApsaraDB RDS for MySQL instance types
The following table lists phased-out ApsaraDB RDS for MySQL instance types. When you create an RDS instance, you cannot select a phased-out instance type. You can upgrade phased-out instance types to some available instance types. You cannot generate an order for an RDS instance that uses a phased-out instance type. For example, you cannot generate an order to change the storage capacity of an RDS instance that uses a phased-out instance type. We recommend that you use the most recent instance type. For more information about how to change the storage capacity of an RDS instance, see Change configuration.
Phased-out instance types cannot support some new features. We recommend that you upgrade a phased-out instance type to the most recent instance type.
Instance type | Number of CPU cores | Memory capacity | Maximum number of connections |
rds.mys2.small | 2 | 240 MB | 60 |
rds.mys2.mid | 4 | 600 MB | 150 |
rds.mys2.standard | 6 | 1,200 MB | 300 |
rds.mys2.large | 8 | 2,400 MB | 600 |
rds.mys2.xlarge | 9 | 6,000 MB | 1,500 |
rds.mys2.2xlarge | 10 | 12,000 MB | 2,000 |
rds.mys2.4xlarge | 11 | 24,000 MB | 2,000 |
rds.mys2.8xlarge | 13 | 48,000 MB | 2,000 |
rds.mysql.st.d13 | 30 | 220 GB | 64,000 |
mysql.x8.medium.3 | 2 | 16 GB | 2,500 |
mysql.x4.large.3 | 4 | 16 GB | 2,500 |
mysql.x8.large.3 | 4 | 32 GB | 5,000 |
mysql.x4.xlarge.3 | 8 | 32 GB | 5,000 |
mysql.x8.xlarge.3 | 8 | 64 GB | 10,000 |
mysql.x4.2xlarge.3 | 16 | 64 GB | 10,000 |
mysql.x8.2xlarge.3 | 16 | 128 GB | 20,000 |
mysql.x4.4xlarge.3 | 32 | 128 GB | 20,000 |
mysql.x8.4xlarge.3 | 32 | 256 GB | 40,000 |
mysql.st.8xlarge.3 | 60 | 470 GB | 100,000 |
mysql.n2.2xlarge.1 | 16 | 32 GB | 10,000 |
mysql.n4.2xlarge.1 | 16 | 64 GB | 15,000 |
mysql.n8.2xlarge.1 | 16 | 128 GB | 20,000 |
mysql.x2.3xlarge2c | 24 | 48 GB | 24,000 |
mysql.n4.4xlarge.1 | 32 | 128 GB | 20,000 |
mysql.n8.4xlarge.1 | 32 | 256 GB | 64,000 |
mysql.n4.8xlarge.1 | 56 | 224 GB | 64,000 |
mysql.n8.8xlarge.1 | 56 | 480 GB | 64,000 |
mysql.n1.micro.1 | 1 | 1 GB | 2,000 |
mysql.n2.small.1 | 1 | 2 GB | 2,000 |