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

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.
• Restore from backup data or from a specific point in time to the original DB instance.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
4. On the Instance Management page, click the target DB instance or click first and then click the target read replica.
5. In the Connection Information area on the Basic Information page, click next to the Database Port field.

   Alternatively, choose Connection Management in the navigation pane on the left. In the Connection Information area, click next to the Database Port field.

   

   RDS for MySQL instances can use database port 2100 to 9500.

   • To submit the change, click .
     • In the dialog box, click Yes.
       1. 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.
       2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will be rebooted.
       3. This process takes 1-5 minutes.
     • In the dialog box, click No to cancel the modification.
   • To cancel the change, click .

6. View the results on the Basic Information page.