From b62e8c8f010f536bf5cc33df42c6136cc956138a Mon Sep 17 00:00:00 2001 From: qiancai Date: Wed, 6 May 2026 14:10:08 +0800 Subject: [PATCH 1/3] clarify serverless private endpoint vpc scope --- tidb-cloud/set-up-private-endpoint-connections-serverless.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tidb-cloud/set-up-private-endpoint-connections-serverless.md b/tidb-cloud/set-up-private-endpoint-connections-serverless.md index 468db50a7d112..beb43823382cd 100644 --- a/tidb-cloud/set-up-private-endpoint-connections-serverless.md +++ b/tidb-cloud/set-up-private-endpoint-connections-serverless.md @@ -53,7 +53,7 @@ To connect to your {{{ .starter }}} or {{{ .essential }}} instance via a private > **Note:** > - > You only need to create one private endpoint per AWS region, which can be shared by all {{{ .starter }}} or {{{ .essential }}} instances located in the same region. + > For each VPC in an AWS Region, you only need to create one private endpoint. The endpoint can be used by all {{{ .starter }}} or {{{ .essential }}} instances in that Region from the same VPC, but cannot be shared across VPCs. ### Step 2. Create an AWS interface endpoint @@ -141,7 +141,7 @@ After you have created the interface endpoint, go back to the TiDB Cloud console > > If you cannot connect to the {{{ .starter }}} or Essential instance, the reason might be that the security group of your VPC endpoint in AWS is not properly set. See [this FAQ](#troubleshooting) for solutions. > -> When creating a VPC endpoint, if you encounter an error `private-dns-enabled cannot be set because there is already a conflicting DNS domain for gatewayXX-privatelink.XX.prod.aws.tidbcloud.com in the VPC vpc-XXXXX`, it is due to that a private endpoint has already been created, and creating a new one is unnecessary. +> When creating a VPC endpoint, if you encounter an error `private-dns-enabled cannot be set because there is already a conflicting DNS domain for gatewayXX-privatelink.XX.prod.aws.tidbcloud.com in the VPC vpc-XXXXX`, a private endpoint has already been created in that VPC, and creating another one for the same private DNS name is unnecessary. ## Troubleshooting From 1a9ae6a4699bbfcba15c86fcc4dcaba51384b3d2 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Wed, 6 May 2026 14:15:45 +0800 Subject: [PATCH 2/3] Update tidb-cloud/set-up-private-endpoint-connections-serverless.md --- tidb-cloud/set-up-private-endpoint-connections-serverless.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/set-up-private-endpoint-connections-serverless.md b/tidb-cloud/set-up-private-endpoint-connections-serverless.md index beb43823382cd..56b472c1ee538 100644 --- a/tidb-cloud/set-up-private-endpoint-connections-serverless.md +++ b/tidb-cloud/set-up-private-endpoint-connections-serverless.md @@ -53,7 +53,7 @@ To connect to your {{{ .starter }}} or {{{ .essential }}} instance via a private > **Note:** > - > For each VPC in an AWS Region, you only need to create one private endpoint. The endpoint can be used by all {{{ .starter }}} or {{{ .essential }}} instances in that Region from the same VPC, but cannot be shared across VPCs. + > For each VPC in an AWS region, you only need to create one private endpoint. The endpoint can be used by all {{{ .starter }}} or {{{ .essential }}} instances in that AWS region from the same VPC, but cannot be shared across VPCs. ### Step 2. Create an AWS interface endpoint From 9ec11017a7763737969c6edd5d81e120f63fa26b Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Wed, 6 May 2026 14:17:11 +0800 Subject: [PATCH 3/3] Update tidb-cloud/set-up-private-endpoint-connections-serverless.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-cloud/set-up-private-endpoint-connections-serverless.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/set-up-private-endpoint-connections-serverless.md b/tidb-cloud/set-up-private-endpoint-connections-serverless.md index 56b472c1ee538..2252f51fe1db0 100644 --- a/tidb-cloud/set-up-private-endpoint-connections-serverless.md +++ b/tidb-cloud/set-up-private-endpoint-connections-serverless.md @@ -141,7 +141,7 @@ After you have created the interface endpoint, go back to the TiDB Cloud console > > If you cannot connect to the {{{ .starter }}} or Essential instance, the reason might be that the security group of your VPC endpoint in AWS is not properly set. See [this FAQ](#troubleshooting) for solutions. > -> When creating a VPC endpoint, if you encounter an error `private-dns-enabled cannot be set because there is already a conflicting DNS domain for gatewayXX-privatelink.XX.prod.aws.tidbcloud.com in the VPC vpc-XXXXX`, a private endpoint has already been created in that VPC, and creating another one for the same private DNS name is unnecessary. +> When creating a VPC endpoint, if you encounter an error `private-dns-enabled cannot be set because there is already a conflicting DNS domain for gatewayXX-privatelink.XX.prod.aws.tidbcloud.com in the VPC vpc-XXXXX`, a private endpoint already exists in that VPC. You do not need to create another one for the same private DNS name. ## Troubleshooting