This topic describes how to view endpoints of a PolarDB cluster compatible with Oracle 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 endpoints.

Primary endpoints

Type Description Supported network type
Primary endpoint A primary endpoint is always destined for the primary node and supports read and write operations. If the primary node fails, the primary endpoint is automatically switched to the read-only node that is promoted to the primary node. Private network
Primary node endpoint (not recommended) The endpoint of the primary node. We recommend that you do not connect directly to the primary node because the node becomes unavailable when it fails. Private network
Read-only node endpoint (not recommended) The endpoint of the read-only node. We recommend that you do not connect directly to the read-only node because the node becomes unavailable when it fails. Private network

Private endpoints

Type Description Scenario
Private endpoint
  • ApsaraDB for PolarDB can achieve optimal performance when it is accessed through the private endpoint.
  • The private endpoint cannot be released.

Examples:

  • If your ECS instance is located in the same VPC as the cluster, then your ECS instance can access the cluster through the private endpoint.
  • You can use DMS to connect to a cluster over a VPC.

Next steps

Connect to a database cluster

Related API operations

API operation Description
DescribeDBClusterEndpoints Queries the endpoint information of a specified PolarDB cluster.
CreateDBEndpointAddress Creates public-facing endpoints for a specified PolarDB cluster.
ModifyDBEndpointAddress Modifies the prefix of the default endpoint and primary endpoint for a specified PolarDB cluster.
DeleteDBEndpointAddress Release an endpoint of a specified PolarDB cluster.