Changing a Database Port

Scenarios

This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the primary DB instance will cause the database port of the standby DB instance to also be changed.

If specific security group rules have been configured for a DB instance, you need to change the inbound rules of the security group to which the DB instance belongs after changing the database port.

Constraints

Changing the database port of a DB instance will cause the instance to reboot.

When the database port of a DB instance is being changed, you cannot:

• Bind an EIP to the DB instance.
• Delete the DB instance.
• Create a backup for the DB instance.

Procedure

1. Log in to the management console.
2. Click in the upper left corner of the page and choose Databases > Relational Database Service.
3. On the Instances page, click the target DB instance or click first and then click the target read replica.
4. In the Connection Information area on the Basic Information page, click Change next to the Database Port field.
   

   RDS for MySQL instances can use database ports 1024 to 65535, excluding 12017, 33071, and 33062, which are reserved for RDS system use.

   • In the displayed dialog box, click Yes.
     • If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
     • If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will reboot.
     • This process takes about 1–5 minutes.
   • In the displayed dialog box, click No to cancel the modification.

5. View the result on the Basic Information page.