To connect to an ApsaraDB RDS for PostgreSQL instance, you must enter the internal or public endpoint and port number of the RDS instance. This topic describes how to view and change the internal and public endpoints and port numbers of an ApsaraDB RDS for PostgreSQL instance in the ApsaraDB RDS console.
Change the internal or public endpoint and port number
FAQ
- After I change a specific endpoint or port number of my RDS instance, do I need to
update the endpoint or port number information on my application?
Yes, after you change a specific endpoint or port number of your RDS instance, you must update the endpoint or port number information on your application. Otherwise, your application cannot connect to your RDS instance.
- After I change a specific endpoint or port number of my RDS instance, is the change
immediately applied? Do I need to restart my RDS instance?
After you change a specific endpoint or port number of your RDS instance, the change is immediately applied. You do not need to restart your RDS instance.
- After I change or release a specific endpoint of my RDS instance, can I use the endpoint
for another RDS instance?
Yes, after you change or release a specific endpoint of your RDS instance, you can use the endpoint 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.