How to Change max_connections on AWS RDS MySQL Using Parameter Groups

Background

MySQL parameters are divided into dynamic (modifiable at runtime with SET GLOBAL) and static (require a reboot). In AWS RDS, all changes must be made through a parameter group ; attempting to run SET GLOBAL max_connections = 1300 results in an error because the required SUPER or SYSTEM_VARIABLES_ADMIN privileges are not available.

Parameter Group Role

RDS uses parameter groups to store engine configuration. By default, an instance is attached to a system‑provided group such as default.mysql8.0. To change static parameters like max_connections, you must create a custom parameter group and apply it to the instance.

Step‑by‑Step Modification of max_connections

1. Identify the Current Parameter Group

aws rds describe-db-instances \
    --db-instance-identifier database1 \
    --query "DBInstances[*].DBParameterGroups[*].DBParameterGroupName" \
    --output text

The output (e.g., default.mysql8.0) shows the group currently attached.

2. Inspect max_connections in the Default Group

aws rds describe-db-parameters \
    --db-parameter-group-name default.mysql8.0 \
    --query "Parameters[?ParameterName=='max_connections']"

The response indicates ApplyMethod is pending-reboot, confirming it is a static parameter.

3. Create a Custom Parameter Group

aws rds create-db-parameter-group \
    --db-parameter-group-name dev-mysql80 \
    --db-parameter-group-family mysql8.0 \
    --description "Custom parameter group for MySQL 8.0"

Make sure the db-parameter-group-family matches the engine version.

4. Modify max_connections in the Custom Group

aws rds modify-db-parameter-group \
    --db-parameter-group-name dev-mysql80 \
    --parameters "ParameterName=max_connections,ParameterValue=1000,ApplyMethod=pending-reboot"

Setting ApplyMethod=pending-reboot signals that the change takes effect after a reboot.

5. Verify the Modification

aws rds describe-db-parameters \
    --db-parameter-group-name dev-mysql80 \
    --query "Parameters[?ParameterName=='max_connections']"

The returned ParameterValue should now be 1000.

6. Bind the Custom Group to the Instance

aws rds modify-db-instance \
    --db-instance-identifier database1 \
    --db-parameter-group-name dev-mysql80 \
    --apply-immediately

The --apply-immediately flag makes the new group active without waiting for the maintenance window, but the static parameter still requires a reboot.

7. Reboot the Instance

aws rds reboot-db-instance \
    --db-instance-identifier database1

Rebooting causes a brief outage; schedule it during low‑traffic periods.

Verification After Reboot

SHOW VARIABLES LIKE 'max_connections';

The output should display max_connections 1000, confirming the change.

Important Considerations

Reboot Requirement : Static parameters like max_connections only take effect after a restart, even if --apply-immediately is used.

Downtime : Expect a few minutes of unavailability; plan for off‑peak hours.

Permission Limits : Direct SET GLOBAL is not allowed on RDS; all changes must go through parameter groups.

Value Range : max_connections accepts 1‑100000, but the optimal value depends on instance memory and workload.

CLI vs Console : The same steps can be performed in the AWS Management Console under RDS → Parameter Groups.

Conclusion

Changing max_connections on an AWS RDS MySQL instance involves checking the current parameter group, creating a custom group, updating the parameter with pending-reboot, attaching the group to the instance, and finally rebooting the instance. Although the process requires a restart, careful planning—such as testing in a non‑production environment and scheduling during low‑traffic windows—minimizes impact.