This topic describes how to view connection endpoints of the POLARDB cluster and introduces primary endpoints and private endpoints.

Procedure

  1. Log on to the ApsaraDB for POLARDB console.
  2. Find the target cluster and click the cluster ID.
  3. In the Connection Information section, view the connection endpoints.

Primary endpoints

Type Description Supported network type
Primary endpoint A primary endpoint always connects to the primary node and supports read and write operations. If the primary node becomes faulty, the primary endpoint is automatically switched to the read-only node that is promoted to the primary node. VPC
Primary node endpoint (not recommended) The endpoint of the primary node. It is not recommended to connect directly to the primary node because the node is unavailable when it fails. VPC
Read-only node endpoint (not recommended) The endpoint of the read-only node. It is not recommended to connect directly to the read-only node because the node is unavailable when it fails. VPC

Private endpoints

Type Description Scenario
Private endpoint
  • POLARDB can achieve optimal performance when accessed through the private endpoint.
  • The private endpoint cannot be released.

For example:

  • If your ECS instance is located in the same VPC as the POLARDB cluster, then your ECS instance can access the POLARDB cluster through the private endpoint.
  • You can access the POLARDB cluster through the private endpoint by using DMS.

Next step

Connect to the cluster. For more information, see Connect to a POLARDB for PostgreSQL cluster.

Related API operations