---
title: "Change Endpoint settings"
slug: "db-clouddbserverless-endpoint"
updated: 2026-10-08T07:09:17Z
published: 2026-10-08T07:09:17Z
canonical: "guide.ncloud-docs.com/db-clouddbserverless-endpoint"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Change Endpoint settings

Available in VPC

When a DB Cluster is created, 1 Write Endpoint and 1 Read Endpoint are automatically created in the subnet where the cluster is located. Endpoint Configuration: Using the Endpoint Configuration menu, you can create additional Write or Read Endpoints in the VPC and subnet where your application is located, or delete previously added endpoints. Endpoints are provided as Private Link-based Endpoint Interfaces on NAVER Cloud Platform, and each created endpoint uses 1 private IP address from the specified subnet.

              Caution

              

- DB management features are available only when the DB Cluster status is **Running**.
- Endpoint creation and deletion operations can be performed one at a time. Once the operation starts, the DB Cluster status changes to **Configuring**. Until the operation is completed and the status returns to **Running**, you cannot perform other endpoint operations or change settings.
- The default Write and Read Endpoints that are automatically created when the cluster is created cannot be deleted. They are deleted together when the cluster is deleted.
- Deleting an endpoint interrupts connections for applications that use that endpoint. Before deleting the endpoint, update the application's connection information to use a different endpoint.
- Endpoints are created as Endpoint Interfaces in the selected subnet and are billed based on the duration of each endpoint's existence. For more information, see [Pricing information](https://www.ncloud.com/product/database/cloudDbServerless).
- The number of endpoints that can be created in a single VPC is subject to the Endpoint Interface limits per VPC defined by Private Link. If the limit is exceeded, the endpoint creation will not be completed. Delete any unused endpoints and try again.

## Endpoint configuration page < a name="Endpoint configuration page">

1. In the VPC environment of the NAVER Cloud Platform console, navigate to **Menu > All Services > Database > Cloud DB Serverless**.
2. Click the **DB Cluster** menu.
3. In the DB Cluster list, select a cluster, then click **[DB management] > Endpoint configuration**.
4. In the endpoint configuration interface, check the list of endpoints for the current cluster.

| Item | Description |
| --- | --- |
| Endpoint type | **Write**: Read/write endpoint (connects to the primary instance)/**Read**: Read-only endpoint (connects to replica instances) |
| Endpoint | Private IP address used by applications to connect. The DB connection port uses the value of **DB Connection Port** in the DB Cluster details. |
| VPC | VPC name where the endpoint is created. |
| Subnet | Subnet where the endpoint is created. `Subnet name \| Zone \| IP address range format is displayed. |
| ACG | ACG name applied to the endpoint. ACG (`cdbserverless-xxxxxxxx`) automatically created by Cloud DB Serverless |
| Status | **Running**: Normal state in which connections are available/**Configuring**: State in which a create or delete operation is in progress. |
| Management | **[Delete]** The default Endpoint that is automatically created when the cluster is created cannot be deleted as the button is deactivated. |

              Note

              

The IP addresses of the default endpoints automatically created when the cluster is created are displayed in **Write Endpoint** and **Read Endpoint** fields of the DB Cluster details. Check the IP addresses of additional endpoints in the endpoint list on the endpoint configuration interface.

## Create Endpoint

1. In the endpoint configuration interface, click **[+ Create Endpoint]**.
2. In the Create Endpoint popup, configure the following settings:

| Item | Description |
| --- | --- |
| Endpoint type | Select either a **Write Endpoint** or **Read Endpoint**. (Required) |
| VPC | Select the VPC where the endpoint will be created. You can select a different VPC within the same account, not just the VPC where the cluster is located. If no VPC exists, click **[Create VPC]** to create one in the VPC console first, and then click the Refresh button. (Required) |
| Subnet | Select the subnet where the endpoint will be created. `Subnet name \| Zone \| Displayed in Public/Private format. Only General-purpose subnets can be selected. Load Balancer-only, Bare Metal-only, and NAT Gateway-only subnets cannot be used. If no subnet exists, click **[Create Subnet]** to create one first, and then click the Refresh button. (Required) |
| ACG settings | This is not separately configured. An ACG for Cloud DB Serverless is automatically created and applied. |

1. Click **[Create]**.
  - The DB Cluster status changes to **Configuring**, and you are redirected to the DB Cluster list interface.
  - When creation is complete, the DB Cluster status returns to **Running**, and the new endpoint is displayed in the endpoint list with a status of **Running**. Typically, the operation is completed within a few minutes.

              Note

              

- If there is no Cloud DB Serverless ACG in the VPC where the endpoint is created, one is automatically created. An inbound rule that allows access to the DB connection port from the IP address range of the selected subnet is also automatically added. Any rules that are manually added by the user to that ACG are retained.
- Outside the subnet range.  

Example: To connect from a Bastion server in a different subnet, add an inbound rule to the ACG by referring to the [ACG](https://guide.ncloud-docs.com/docs/en/vpc-acg-vpc) guide.

## Delete Endpoint

1. In the endpoint list on the endpoint configuration interface, click **[Delete]** for the endpoint you want to delete.
2. In the Delete Endpoint popup, verify the endpoint type and IP address of the endpoint to be deleted, and then click **[Delete]**.
  - The DB Cluster status changes to **Configuring**, and you are redirected to the DB Cluster list interface.
  - When the deletion is complete, the DB Cluster status returns to **Running**, and the endpoint is removed from the endpoint list.

              Caution

              

Deleting an endpoint interrupts connections for applications that use that endpoint. Before deleting the endpoint, update the application's connection information to use a different endpoint.

              Note

              

- When an endpoint is deleted, the ACG inbound rule for the corresponding subnet range is also removed. If other endpoints using the same subnet remain, the rule is retained.
- If the last endpoint in a VPC other than the VPC where the cluster is located is deleted, the Cloud DB Serverless-dedicated ACG for that VPC is also deleted. If that ACG is being used for other resources, it is not deleted.

## Configuring status

If an endpoint creation or deletion operation is in progress, the status of the corresponding endpoint is displayed as **Configuring**, and both **[Delete]** and **[+ Create Endpoint]** are disabled. Once the operation is complete and the DB Cluster status returns to Running, the features become available again.

              Note

              

- If endpoint creation or deletion operations are in progress for other endpoints in the same VPC, completion may be delayed depending on the processing order of Private Link. The operation is retried automatically.
- To use Endpoint Configuration with a Sub Account, you need a policy that allows the `View/getEndpointInterfaceList`, `Change/createEndpointInterface`, and `Change/deleteEndpointInterface` actions. For more information, see [Cloud DB Serverless permissions management](/docs/en/db-clouddbserverless-subaccount).