- Documentation
RDS for MySQL
User guide
Managing parameters
Modifying maximum connections
Managing parameters
Modifying maximum connections
Modifying maximum connections
This topic describes how to modify the max connections for an RDS for MySQL instance.
Background
For services that require high concurrency, set a sufficient number of connections to prevent users from being unable to access the database. Therefore, RDS for MySQL instances support modifying max connections through the console and API to accommodate an increase in connection demands.
Precautions
- Supported versions: MySQL 5.7, MySQL 8.0, and MySQL 8.4.
- The default max connections vary depending on the instance specifications. Therefore, when you change the specifications of a primary/standby or read-only node, the max connections value changes accordingly. However, if you previously modified the max connections, the value will remain unchanged after a specification change. In this case, you must manually adjust the max connections to a reasonable value. If you do not modify the value, the previously reasonable max connections value will be too high after you downgrade the specifications, which may cause a memory overflow.
Impact
Database connections use memory and CPU resources. The more connections you have, the more resources are consumed. When setting the max connections, consider the availability of database resources and set the value carefully. If max_connections is set too high, it can easily cause out-of-memory errors. Therefore, we recommend using the default max connections value for the MySQL instance to prevent performance degradation and instability caused by improper configuration.
Parameter description
Modification method
After making the changes, you can check the Records of MySQL parameter modification tab to see if the modified maximum connection count parameter value has taken effect.
Last updated: 2026.05.28 15:17:50