Starting September 19, 2025 (Singapore Time), the default maximum number of connections and maximum IOPS have been increased for specific dedicated ApsaraDB RDS for MySQL instances with Premium Local SSDs. No additional fees apply.
Scope
This change applies to specific dedicated instance types of primary ApsaraDB RDS for MySQL instances with Premium Local SSDs. For the full list of affected instance types, see Instance types for primary ApsaraDB RDS for MySQL instances (Standard Edition).
Phased-out instance types are not affected. To benefit from the updated limits, change your instance to an available instance type.
How the change takes effect
The effective date depends on when your instance was created:
Instances created on or after September 19, 2025 (Singapore Time): The increased limits apply automatically — no action required.
Instances created before September 19, 2025 (Singapore Time): The increased limits apply only after you restart the instance or change its specifications.
ImportantRestarting an instance causes a brief disconnection of approximately 30 seconds. Make sure your application has an automatic reconnect mechanism, and schedule the restart during a low-traffic window.
Potential impacts
An increase in maximum IOPS raises the denominator in the IOPS utilization formula:
IOPS utilization = Actual IOPS used / Maximum IOPS for the instanceAfter the change takes effect, you may see a sudden drop in monitored IOPS utilization. This is expected behavior, not a performance issue.
New limits by instance type
The following table shows the updated maximum connections and maximum IOPS for each affected dedicated instance type.
| Instance family | Instance type | CPU and memory | Max connections before | Max connections after | Max IOPS before | Max IOPS after |
|---|---|---|---|---|---|---|
| Dedicated | mysql.x8.medium.2 | 2 cores, 16 GB | 2,500 | 8,000 | 15,000 | 30,000 |
| Dedicated | mysql.x4.large.2 | 4 cores, 16 GB | 2,500 | 8,000 | 30,000 | 40,000 |
| Dedicated | mysql.x8.large.2 | 4 cores, 32 GB | 5,000 | 12,000 | 40,000 | 60,000 |
| Dedicated | mysql.x4.xlarge.2 | 8 cores, 32 GB | 5,000 | 12,000 | 45,000 | 60,000 |
| Dedicated | mysql.x8.xlarge.2 | 8 cores, 64 GB | 10,000 | 16,000 | 50,000 | 90,000 |
| Dedicated | mysql.x4.2xlarge.2 | 16 cores, 64 GB | 10,000 | 16,000 | 60,000 | 75,000 |
| Dedicated | mysql.x8.2xlarge.2 | 16 cores, 128 GB | 20,000 | 32,000 | 60,000 | 105,000 |
| Dedicated | mysql.x4.4xlarge.2 | 32 cores, 128 GB | 20,000 | 32,000 | 80,000 | 105,000 |
| Dedicated | mysql.x6.4xlarge.2 | 32 cores, 192 GB | — | — | 95,000 | 120,000 |
| Dedicated | mysql.x8.4xlarge.2 | 32 cores, 256 GB | — | — | 100,000 | 135,000 |
Verify the updated limits
To confirm that the new limits are in effect on your instance:
Go to the RDS console and click the instance ID.
In the Configuration Information section of the instance details page, check the values of Maximum Connections and Maximum IOPS.