All Products
Search

This Product

    ApsaraDB RDS:Instance types for standard primary ApsaraDB RDS for MySQL instances (original x86 architecture)

    Document Center

    ApsaraDB RDS:Instance types for standard primary ApsaraDB RDS for MySQL instances (original x86 architecture)

    Last Updated:Feb 27, 2026

    This document lists all available instance types for standard primary ApsaraDB RDS for MySQL instances on the original x86 architecture. Use this reference to select the right combination of CPU, memory, connections, IOPS, and storage for your workload. Instance types are organized by RDS edition and instance family.

    For more information about the differences between standard and YiTian product types, see Product types.

    Before you begin

    Keep the following points in mind when selecting an instance type:

    • Availability: Some instance types may no longer be available. You can select only the instance types that are available on the ApsaraDB RDS buy page. The supported instance types vary based on regions, and the instance types displayed on the buy page shall prevail. If you cannot select the required instance type when you change the specifications of an RDS instance, the instance type is not supported in that region.

    • Serverless instances: The resources of RDS for MySQL Serverless instances are measured by RCUs instead of CPU cores and memory. However, the instance type codes of these instances keep the same format as other RDS instances to avoid compatibility issues. The instance type codes for RDS for MySQL Serverless instances include mysql.n2.serverless.1c (instances running Basic Edition) and mysql.n2.serverless.2c (instances running High-availability Edition).

    • Standard SSD deprecation: The standard SSD storage type is no longer available for purchase for some RDS instances. You can select the Enterprise SSD (ESSD) storage type that delivers high performance. For more information, see [EOS/Discontinuation] End of sale for the standard SSD storage type for specific database engines in ApsaraDB RDS from July 01, 2022.

    • Maximum connections: The maximum number of connections in this topic indicates the maximum number of processes that can be connected to the RDS instance at a time.

    • Public bandwidth: The public bandwidth of an RDS instance cannot be adjusted.

    Quick reference: instance families

    Instance familyDescriptionScenarios
    General-purposeUtilizes resource multiplexing to balance cost and performance stability. Does not guarantee maximum IOPS or maximum I/O bandwidth.Application scenarios that have low requirements for performance stability or require a balance between performance and cost.
    DedicatedDedicates most resources to ensure long-term performance stability. Performance is not affected by other instances on the same physical machine.Scenarios in which the database is used as a core system.
    Dedicated hostFully dedicates all resources of a physical server. This is the top-tier configuration of the dedicated instance family. Supported only by instances that use Premium Local SSDs.Scenarios in which the database is a core system, such as in finance, e-commerce, government, and large- to medium-sized Internet business.

    For more information about instance families, see Instance families.

    RDS instances on RDS Basic Edition (with cloud disks)

    Important

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

    Supported storage types and capacity ranges:

    • PL0 ESSD: 10 GB to 32,000 GB

    • PL1 ESSD: 20 GB to 64,000 GB

    • Premium ESSD: 10 GB to 64,000 GB

    • Standard SSD: 20 GB to 6,000 GB

    RDS editionInstance familyInstance typeCPU and memoryMaximum number of connections (default value)Maximum IOPSMaximum I/O bandwidth (Mbit/s)
    RDS Basic EditionGeneral-purposemysql.n2.medium.12 cores, 4 GB4,000General-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(see note)
    mysql.n4.medium.12 cores, 8 GB6,000
    mysql.n2.large.14 cores, 8 GB6,000
    mysql.n4.large.14 cores, 16 GB8,000
    mysql.n2.xlarge.18 cores, 16 GB8,000
    mysql.n4.xlarge.18 cores, 32 GB10,000

    RDS instances on RDS High-availability Edition (with cloud disks)

    Important

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

    Supported storage types and capacity ranges:

    • PL1 ESSD: 20 GB to 64,000 GB

    • PL2 ESSD: 500 GB to 64,000 GB

    • PL3 ESSD: 1,500 GB to 64,000 GB

    • Premium ESSD: 10 GB to 64,000 GB

    • Standard SSD: 20 GB to 6,000 GB

    General-purpose instance types

    Instance typeCPU and memoryMaximum number of connections (default value)Maximum IOPSMaximum I/O bandwidth (Mbit/s)
    mysql.n2.small.2c1 core, 2 GB2,000General-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.(see note)
    mysql.n2.medium.2c2 cores, 4 GB4,000

    Dedicated instance types

    Instance typeCPU and memoryMaximum number of connections (default value)Maximum IOPSMaximum I/O bandwidth (Mbit/s)
    mysql.x2.medium.2c2 cores, 4 GB4,00010,000125
    mysql.x4.medium.2c2 cores, 4 GB6,000
    mysql.x8.medium.2c2 cores, 16 GB8,000
    mysql.x2.large.2c4 cores, 8 GB6,00020,000187.5
    mysql.x4.large.2c4 cores, 16 GB8,000
    mysql.x8.large.2c4 cores, 32 GB12,000
    mysql.x2.xlarge.2c8 cores, 16 GB8,00025,000250
    mysql.x4.xlarge.2c8 cores, 32 GB10,000
    mysql.x8.xlarge.2c8 cores, 64 GB16,000
    mysql.x2.3large.2c12 cores, 24 GB12,00030,000312.5
    mysql.x4.3large.2c12 cores, 48 GB15,000
    mysql.x8.3large.2c12 cores, 96 GB24,000
    mysql.x2.2xlarge.2c16 cores, 32 GB16,00040,000375
    mysql.x4.2xlarge.2c16 cores, 64 GB20,000
    mysql.x8.2xlarge.2c16 cores, 128 GB32,000
    mysql.x2.3xlarge.2c24 cores, 48 GB24,00050,000500
    mysql.x4.3xlarge.2c24 cores, 96 GB30,000
    mysql.x8.3xlarge.2c24 cores, 192 GB48,000
    mysql.x2.4xlarge.2c32 cores, 64 GB32,00060,000625
    mysql.x4.4xlarge.2c32 cores, 128 GB40,000
    mysql.x8.4xlarge.2c32 cores, 256 GB64,000
    mysql.x2.13large.2c52 cores, 96 GB52,000100,0001,000
    mysql.x4.13large.2c52 cores, 192 GB65,000
    mysql.x8.13large.2c52 cores, 384 GB104,000
    mysql.x2.8xlarge.2c64 cores, 128 GB64,000120,0001,025
    mysql.x4.8xlarge.2c64 cores, 256 GB80,000150,000
    mysql.x8.8xlarge.2c64 cores, 512 GB128,000150,000
    mysql.x2.13xlarge.2c104 cores, 192 GB104,000200,0002,000
    mysql.x4.13xlarge.2c104 cores, 384 GB130,000200,0002,000
    mysql.x8.13xlarge.2c104 cores, 768 GB208,000200,0002,000
    mysql.x4.16xlarge.2c128 cores, 512 GB128,000300,0002,560

    RDS for MySQL supports automatic storage scaling when the storage usage reaches a specified threshold. For more information, see Configure automatic expansion for cloud disks.

    RDS instances on RDS Cluster Edition (with cloud disks)

    RDS for MySQL instances that run RDS Cluster Edition support MySQL 5.7 and MySQL 8.0.

    Important

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

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

    Supported storage types and capacity ranges:

    • PL1 ESSD: 20 GB to 64,000 GB

    • PL2 ESSD: 500 GB to 64,000 GB

    • PL3 ESSD: 1,500 GB to 64,000 GB

    • Premium ESSD: 10 GB to 64,000 GB

    General-purpose instance types

    Instance typeCPU and memoryMaximum number of connections (default value)Maximum IOPSMaximum I/O bandwidth (Mbit/s)
    mysql.n2.medium.xc2 cores, 4 GB4,000General-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.(see note)
    mysql.n4.medium.xc2 cores, 8 GB6,000
    mysql.n8.medium.xc2 cores, 16 GB8,000
    mysql.n2.large.xc4 cores, 8 GB6,000
    mysql.n4.large.xc4 cores, 16 GB8,000
    mysql.n8.large.xc4 cores, 32 GB12,000
    mysql.n2.xlarge.xc8 cores, 16 GB12,000
    mysql.n4.xlarge.xc8 cores, 32 GB12,000
    mysql.n8.xlarge.xc8 cores, 64 GB16,000

    Dedicated instance types

    Instance typeCPU and memoryMaximum number of connections (default value)Maximum IOPSMaximum I/O bandwidth (Mbit/s)
    mysql.x2.medium.xc2 cores, 4 GB4,00010,000125
    mysql.x4.medium.xc2 cores, 8 GB6,000
    mysql.x8.medium.xc2 cores, 16 GB8,000
    mysql.x2.large.xc4 cores, 8 GB6,00020,000187.5
    mysql.x4.large.xc4 cores, 16 GB8,000
    mysql.x8.large.xc4 cores, 32 GB12,000
    mysql.x2.xlarge.xc8 cores, 16 GB12,00025,000250
    mysql.x4.xlarge.xc8 cores, 32 GB12,000
    mysql.x8.xlarge.xc8 cores, 64 GB16,000
    mysql.x2.3large.xc12 cores, 24 GB12,00030,000312.5
    mysql.x4.3large.xc12 cores, 48 GB15,000
    mysql.x8.3large.xc12 cores, 96 GB24,000
    mysql.x2.2xlarge.xc16 cores, 32 GB16,00040,000375
    mysql.x4.2xlarge.xc16 cores, 64 GB20,000
    mysql.x8.2xlarge.xc16 cores, 128 GB32,000
    mysql.x2.3xlarge.xc24 cores, 48 GB24,00050,000500
    mysql.x4.3xlarge.xc24 cores, 96 GB30,000
    mysql.x8.3xlarge.xc24 cores, 192 GB48,000
    mysql.x2.4xlarge.xc32 cores, 64 GB32,00060,000625
    mysql.x4.4xlarge.xc32 cores, 128 GB40,000
    mysql.x8.4xlarge.xc32 cores, 256 GB64,000
    mysql.x2.13large.xc52 cores, 96 GB52,000100,0001,000
    mysql.x4.13large.xc52 cores, 192 GB65,000
    mysql.x8.13large.xc52 cores, 384 GB104,000
    mysql.x2.8xlarge.xc64 cores, 128 GB64,000120,0001,025
    mysql.x4.8xlarge.xc64 cores, 256 GB80,000150,0001,025
    mysql.x8.8xlarge.xc64 cores, 512 GB128,000150,0001,000
    mysql.x2.13xlarge.xc104 cores, 192 GB104,000200,0002,000
    mysql.x4.13xlarge.xc104 cores, 384 GB130,000
    mysql.x8.13xlarge.xc104 cores, 768 GB208,000

    RDS for MySQL supports automatic storage scaling when the storage usage reaches a specified threshold. For more information, see Configure automatic expansion for cloud disks.

    RDS instances on RDS High-availability Edition (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 will be increased. For more information, see [Product/Feature Change] Increased Default Maximum Connections and Maximum IOPS for RDS for MySQL Instances with Premium Local SSDs.

    General-purpose instance types

    Instance typeCPU and memoryMaximum number of connections (default value)Maximum IOPSStorage capacity
    rds.mysql.t1.small1 core, 1 GB3001,2005 GB to 3,000 GB
    rds.mysql.s1.small1 core, 2 GB6002,000
    rds.mysql.s2.large2 cores, 4 GB1,2004,000
    rds.mysql.s2.xlarge2 cores, 8 GB2,0006,000
    rds.mysql.s3.large4 cores, 8 GB2,0008,000
    rds.mysql.m1.medium4 cores, 16 GB4,00014,000
    rds.mysql.c1.large8 cores, 16 GB4,00020,0005 GB to 4,000 GB
    rds.mysql.c1.xlarge8 cores, 32 GB8,00028,000
    rds.mysql.c2.xlarge16 cores, 64 GB16,00040,00020 GB to 12,000 GB
    rds.mysql.c2.xlp216 cores, 96 GB24,00040,000

    Dedicated instance types

    Instance typeCPU and memoryMaximum number of connections (default value)Maximum IOPSStorage capacity
    mysql.x2.medium.22 cores, 4 GB4,00015,00020 GB to 3,000 GB
    mysql.x4.medium.22 cores, 8 GB6,00020,000
    mysql.x6.medium.22 cores, 12 GB7,00025,000
    mysql.x8.medium.22 cores, 16 GB8,00030,000
    mysql.x2.large.24 cores, 8 GB6,00030,000
    mysql.x4.large.24 cores, 16 GB8,00040,000
    mysql.x6.large.24 cores, 24 GB10,00040,000
    mysql.x8.large.24 cores, 32 GB12,00060,000
    mysql.x2.xlarge.28 cores, 16 GB8,00045,00020 GB to 4,000 GB
    mysql.x4.xlarge.28 cores, 32 GB12,00060,000
    mysql.x6.xlarge.28 cores, 48 GB14,00060,000
    mysql.x8.xlarge.28 cores, 64 GB16,00090,000
    mysql.x2.2xlarge.216 cores, 32 GB12,00060,00020 GB to 12,000 GB
    mysql.x4.2xlarge.216 cores, 64 GB16,00075,000
    mysql.x6.2xlarge.216 cores, 96 GB24,00075,000
    mysql.x8.2xlarge.216 cores, 128 GB32,000105,000
    mysql.x2.4xlarge.232 cores, 64 GB16,00080,00020 GB to 16,000 GB
    mysql.x4.4xlarge.232 cores, 128 GB32,000105,000
    mysql.x6.4xlarge.232 cores, 192 GB36,000120,000
    mysql.x8.4xlarge.232 cores, 256 GB40,000135,000
    mysql.x2.8xlarge.264 cores, 128 GB32,000140,000
    mysql.x4.8xlarge.264 cores, 256 GB40,000150,000
    mysql.x6.8xlarge.264 cores, 384 GB60,000150,000
    mysql.x8.8xlarge.264 cores, 512 GB80,000150,000

    Dedicated host instance types

    Instance typeCPU and memoryMaximum number of connections (default value)Maximum IOPSStorage capacity
    rds.mysql.st.h4360 cores, 470 GB100,000150,000
    rds.mysql.st.v5290 cores, 720 GB150,000150,000

    Phased-out ApsaraDB RDS for MySQL instance types

    The following table lists phased-out ApsaraDB RDS for MySQL instance types. These instance types have the following restrictions:

    • You cannot select a phased-out instance type when you create an RDS instance.

    • 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 instance configurations.

    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 typeNumber of CPU coresMemory capacityMaximum number of connections
    rds.mys2.small2240 MB60
    rds.mys2.mid4600 MB150
    rds.mys2.standard61,200 MB300
    rds.mys2.large82,400 MB600
    rds.mys2.xlarge96,000 MB1,500
    rds.mys2.2xlarge1012,000 MB2,000
    rds.mys2.4xlarge1124,000 MB2,000
    rds.mys2.8xlarge1348,000 MB2,000
    rds.mysql.st.d1330220 GB64,000
    mysql.x8.medium.3216 GB2,500
    mysql.x4.large.3416 GB2,500
    mysql.x8.large.3432 GB5,000
    mysql.x4.xlarge.3832 GB5,000
    mysql.x8.xlarge.3864 GB10,000
    mysql.x4.2xlarge.31664 GB10,000
    mysql.x8.2xlarge.316128 GB20,000
    mysql.x4.4xlarge.332128 GB20,000
    mysql.x8.4xlarge.332256 GB40,000
    mysql.st.8xlarge.360470 GB100,000
    mysql.n2.2xlarge.11632 GB10,000
    mysql.n4.2xlarge.11664 GB15,000
    mysql.n8.2xlarge.116128 GB20,000
    mysql.x2.3xlarge2c2448 GB24,000
    mysql.n4.4xlarge.132128 GB20,000
    mysql.n8.4xlarge.132256 GB64,000
    mysql.n4.8xlarge.156224 GB64,000
    mysql.n8.8xlarge.156480 GB64,000
    mysql.n1.micro.111 GB2,000
    mysql.n2.small.112 GB2,000