Skip to content

cloud: clarify serverless private endpoint VPC scope #22849

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
qiancai wants to merge 3 commits into
base: release-8.5
Choose a base branch
from
+2 −2
Open

cloud: clarify serverless private endpoint VPC scope #22849

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b62e8c8
clarify serverless private endpoint vpc scope
qiancai May 6, 2026
1a9ae6a
Update tidb-cloud/set-up-private-endpoint-connections-serverless.md
qiancai May 6, 2026
9ec1101
Update tidb-cloud/set-up-private-endpoint-connections-serverless.md
qiancai May 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions tidb-cloud/set-up-private-endpoint-connections-serverless.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 AWS region from the same VPC, but cannot be shared across VPCs.
Copy link
Copy Markdown
Collaborator

@hfxsd hfxsd May 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> 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.
> 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 the same VPC of that AWS region , but cannot be shared across VPCs.


### Step 2. Create an AWS interface endpoint

Expand Down Expand Up @@ -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 already exists in that VPC. You do not need to create another one for the same private DNS name.

## Troubleshooting

Expand Down
Loading