ApsaraDB RDS:View and change the endpoints and port numbers

Prerequisites

• A whitelist is configured. For more information, see Configure an IP address whitelist.

• A public endpoint for the RDS instance is available. For more information, see Apply for or release a public endpoint.

Usage notes

If you change the endpoint or port number of your RDS instance, you must update the endpoint or port number information on your application. If you do not update the information, your application cannot connect to your RDS instance.

Procedure

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. In the left-side navigation pane of the page that appears, click Database Connection to view the internal and public endpoints and ports of the RDS instance.

3. In the Database Connection section of the page that appears, click Modify Endpoint.

4. Set the Connection Type parameter to Internal Endpoint or Public Endpoint. Then, configure the Endpoint and Port parameters and click Ok.

   Note

   • The prefix of an endpoint must be 8 to 64 characters in length and can contain letters, digits, and hyphens (-). The prefix must start with a lowercase letter.

   • The port number must be within the range of 1000 to 5999.

FAQ

• Do I need to modify the endpoint or port number in my application after I modify the endpoint or port number of an RDS instance?

  Yes, you must modify the endpoint or port number in the application after you have modified them. Otherwise, the application cannot connect to the RDS instance.

• Does the modification of the endpoint immediately take effect? Do I need to restart my RDS instance?

  No, you do not need to restart the instance. The modification takes effect immediately.

• After I change or release an endpoint of my RDS instance, can I use the endpoint for another RDS instance?

  Yes, you can use the changed or released endpoint for another RDS instance.

• Does a primary/secondary switchover on an RDS instance trigger changes to the endpoints of the RDS instance?

  No, a primary/secondary switchover does not trigger changes to the endpoints of your RDS instance. However, the IP addresses that are associated with the endpoints change. Your application can still connect to your RDS instance by using the endpoints.

Prerequisites

• The RDS instance runs SQL Server EE on RDS Cluster Edition.

• A read-only routing endpoint is enabled for the RDS instance. For more information, see Enable the read-only routing endpoint to implement read/write splitting.

Usage notes

• When you disable the read-only routing endpoint for your RDS instance, a transient connection that lasts 30 seconds or less occurs. We recommend that you disable the read-only routing endpoint during off-peak hours and make sure that your application is configured to automatically reconnect to the RDS instance. This prevents interruptions to your workloads.

• After you disable the read-only routing endpoint, it becomes invalid. Before you disable the read-only routing endpoint, make sure that your application no longer uses this endpoint.

Procedure

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. In the left-side navigation pane of the page that appears, click Cluster Management to view the read-only routing endpoint and port.

3. In the Basic Information section, click Disable Readonly Splitting Address.

   

4. In the message that appears, click OK.