When you connect to an ApsaraDB RDS for MySQL instance, you must enter the internal or public endpoint and port number of the instance. This topic describes how to view and change the internal and public endpoints and port numbers of an ApsaraDB RDS for MySQL instance in the ApsaraDB RDS console.
View the internal and public endpoints and port numbers of an RDS instance in the new ApsaraDB RDS console
Change the internal or public endpoint and port number of an RDS instance
FAQ
- After I change an endpoint or a port number of my RDS instance, do I need to update
the endpoint or port number information in my application?
Yes, after you change an endpoint or a 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.
- After I change an endpoint or a port number of my RDS instance, does the change immediately
take effect? Do I need to restart my RDS instance?
After you change an endpoint or a port number of your RDS instance, the change immediately takes effect. You do not need to restart your RDS instance.
- After I change or release an endpoint of my RDS instance, can I use the endpoint for
another RDS instance?
Yes, after you change or release an endpoint of your RDS instance, you can use the endpoint of your RDS instance for another RDS instance.
- Does a primary/secondary switchover trigger changes to the endpoints of my 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.
References
For more information about the endpoints that are used to connect to the dedicated proxy of an RDS instance, see Manage the dedicated proxy endpoints of an ApsaraDB RDS for MySQL instance.