When you connect to an ApsaraDB RDS for MySQL instance, you must enter its internal or public endpoint and port number. 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)
View the internal and public endpoints and port numbers of an RDS instance (in the original ApsaraDB RDS console)
Change the internal or public endpoint and port number of an RDS instance
FAQ
- After I change an endpoint or port number of my RDS instance, do I need to update
the endpoint or port number on my application?
Yes, after you change an endpoint or port number of your RDS instance, you must update the endpoint or port number on your application. Otherwise, your application cannot connect to your RDS instance.
- After I change an endpoint or port number of my RDS instance, is the change immediately
applied? And do I need to restart my RDS instance?
After you change an endpoint or port number of your RDS instance, the change is immediately applied and you do not need to restart your RDS instance.
- After I change or release an endpoint of my RDS instance, can the endpoint be used
for another RDS instance?
Yes, after you change or release an endpoint of your RDS instance, the endpoint can be used 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 dedicated proxy endpoint of an RDS instance, see Create a proxy endpoint for a dedicated proxy.