Docs

RDS for PostgreSQL

Managing connection endpoints

Editing connection endpoints

RDS for PostgreSQL supports modifying the connection information, endpoint information, and read/write separation settings of connection endpoints. This topic describes how to edit connection endpoints.

Prerequisites

An instance is created and in the Running state. For details, see Creating an instance.

Procedure

In the upper-left corner of the top menu bar, select the project and region for the instance.

tip

If the project of the instance has not been set, the project should be selected as All resources.

On the Instances page, click the name of target instance and enter Summary page.

Click on the Connectivity tab and hover over the target endpoint card in the Instance topology section. Click Modify endpoint in the pop-up window to open the Modify endpoint page.

At the Modify endpoint page, you can modify the private address prefix, private network port, enable or disable Internet access, enable or disable inner service zone access, and other settings following the procedure below.

Actions	Note
Modify private network access port	For more information, refer to Modify private network port.
Enable public network access	For more information, refer to Enabling public network access.
Disable public network access	For more information, refer to Disabling public network access.
Enable public service area access	For more information, refer to Enabling public service area access.
Disable public service area access	For more information, refer to Disable public service area access.
Change the name of a connection endpoint	The rules for the endpoint name are as follows: - The name only supports Chinese characters, letters, digits, underscores ( _ ), and hyphens ( - ). - Cannot start with digits or hyphens. - Length must be 1 to 64 characters. Modification fails if left empty, and the original endpoint name remains.
Enable or disable read/write separation	For more information, refer to Enabling or disabling read/write separation. tip This feature is limited to the default endpoint only.
Set the number of read/write separation proxy connections	Set the number of read/write separation proxy connections for the default endpoint. The minimum number of proxy connections is 20; the maximum depends on the specification of the instance's primary node. Different specifications support different maximum proxy connections. For details, refer to Product specifications. tip This feature is limited to the default endpoint only. When modifying the number of read/write separation proxy connections, the instance may experience a flash disconnection within seconds, operate with caution. It is recommended that you set a reconnection mechanism for your application to reduce the impact on your business.
Set read-only latency threshold	The value range of the read-only latency threshold is 0~3600s. Once a read-only latency threshold is set, read-only nodes with a latency that exceeds this value will not be assigned read-only requests. tip This feature is supported only by the default endpoint and can only be configured when the instance has a read-only node, the instance has another read-write endpoint with read-write separation feature is enabled.
Set the allocation method of read/write separation weights.	Read/Write separation weights are allocated automatically by default. On the Modify endpoint page, allocation weights can be customized. For more information about how to customize read/write splitting weights, refer to Setting read/write separation weights. tip This feature is supported only by the default endpoint and can only be configured when the instance has a read-only node, the instance has another read-write endpoint with read-write separation feature is enabled.
Disable primary node	After enabling, the primary node of the endpoint will reject all requests. tip This feature is supported only by the default endpoint and can only be configured when the instance has a read-only node, the instance has another read-write endpoint with read-write separation feature is enabled, and the read-write separation weight allocation method is set to custom allocation. After enabling, the primary node of the endpoint will reject all requests. read requests will be distributed to read-only nodes whose read weight is not 0. Pay attention to the resulting business impact. all connections through the endpoint will be disconnected for a few seconds. Handle with caution. It is recommended to add a reconnection mechanism to your application to greatly reduce the impact of database connection interruptions on your business.

Complete the above settings and click OK.

Last updated: 2026.02.04 17:20:35