Skip to content

Add private endpoint management tips. #23612

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

Merged
ti-chi-bot merged 5 commits into from
Aug 28, 2026
+10 −0
Merged

Add private endpoint management tips. #23612

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5c0f503
Add private endpoint management tips.
ginkgoch Aug 26, 2026
894b7e4
Add same region restriction
ginkgoch Aug 27, 2026
ae0ae78
Apply suggestion from @qiancai
ginkgoch Aug 28, 2026
e6bdacc
Apply suggestion from @qiancai
ginkgoch Aug 28, 2026
a567b7d
Apply suggestion from @qiancai
ginkgoch Aug 28, 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
5 changes: 5 additions & 0 deletions tidb-cloud/premium/set-up-sink-private-endpoint-premium.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,11 @@ For more information about roles in TiDB Cloud, see [User roles](/tidb-cloud/man

Private endpoints leverage the **Private Link** technology from cloud providers, enabling resources in your VPC to connect to services in other VPCs through private IP addresses, as if those services were hosted directly within your VPC.

> **Note:**
>
> - A private endpoint is an organization-level resource and is not tied to a specific {{{ .premium }}} instance. Private endpoints created within the same organization and in the same region can be shared by multiple instances connecting to the same downstream service, so you do not need to create a separate endpoint for each instance.
> - Deleting a {{{ .premium }}} instance does not delete its private endpoints. A private endpoint is automatically deleted if it is not used by any instance for 30 days, even if the instances that previously used it remain available. You can also manually delete a private endpoint when it is no longer needed. However, you cannot delete it while it is in use by any instance.

Comment thread
ginkgoch marked this conversation as resolved.
<SimpleTab>
<div label="AWS">

Expand Down
5 changes: 5 additions & 0 deletions tidb-cloud/set-up-sink-private-endpoint.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,11 @@ For more information about roles in TiDB Cloud, see [User roles](/tidb-cloud/man

Private endpoints leverage **Private Link** or **Private Service Connect** technologies from cloud providers, enabling resources in your VPC to connect to services in other VPCs through private IP addresses, as if those services were hosted directly within your VPC.

> **Note:**
>
> - A private endpoint is a project-level resource and is not tied to a specific cluster. Private endpoints created within the same project and in the same region can be shared by multiple TiDB Cloud Dedicated clusters connecting to the same downstream service, so you do not need to create a separate endpoint for each cluster.
> - Deleting a cluster does not delete its private endpoints. A private endpoint is automatically deleted if it is not used by any cluster for 30 days, even if the clusters that previously used it remain available. You can also manually delete a private endpoint when it is no longer needed. However, you cannot delete it while it is in use by any cluster.

<SimpleTab>
<div label="AWS">

Expand Down