From 5c0f5035beecb91f760ce6f21ec4e7057ecd2aa7 Mon Sep 17 00:00:00 2001 From: Howard Chen Date: Wed, 26 Aug 2026 14:29:34 +0800 Subject: [PATCH 1/5] Add private endpoint management tips. --- tidb-cloud/premium/set-up-sink-private-endpoint-premium.md | 4 ++++ tidb-cloud/set-up-sink-private-endpoint.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md b/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md index 452fa92897c39..6e63373faaf3c 100644 --- a/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md +++ b/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md @@ -25,6 +25,10 @@ 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 a tenant-level resource and is not tied to a specific instance. Private endpoints created within the same tenant 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 an instance does not delete its private endpoints. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any instance. +
diff --git a/tidb-cloud/set-up-sink-private-endpoint.md b/tidb-cloud/set-up-sink-private-endpoint.md index b5c73a3a5cd0b..4f3dcb0eaf6ac 100644 --- a/tidb-cloud/set-up-sink-private-endpoint.md +++ b/tidb-cloud/set-up-sink-private-endpoint.md @@ -30,6 +30,10 @@ 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 can be shared by multiple 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. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any cluster. +
From 894b7e49c083e4b47a31fb5b576f8048b851ce4c Mon Sep 17 00:00:00 2001 From: Howard Chen Date: Thu, 27 Aug 2026 10:23:41 +0800 Subject: [PATCH 2/5] Add same region restriction --- tidb-cloud/premium/set-up-sink-private-endpoint-premium.md | 2 +- tidb-cloud/set-up-sink-private-endpoint.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md b/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md index 6e63373faaf3c..8307673b32566 100644 --- a/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md +++ b/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md @@ -27,7 +27,7 @@ Private endpoints leverage the **Private Link** technology from cloud providers, > **Note:** > -> A private endpoint is a tenant-level resource and is not tied to a specific instance. Private endpoints created within the same tenant 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 an instance does not delete its private endpoints. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any instance. +> A private endpoint is a tenant-level resource and is not tied to a specific instance. Private endpoints created within the same tenant 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 an instance does not delete its private endpoints. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any instance.
diff --git a/tidb-cloud/set-up-sink-private-endpoint.md b/tidb-cloud/set-up-sink-private-endpoint.md index 4f3dcb0eaf6ac..340c3ffd7e495 100644 --- a/tidb-cloud/set-up-sink-private-endpoint.md +++ b/tidb-cloud/set-up-sink-private-endpoint.md @@ -32,7 +32,7 @@ Private endpoints leverage **Private Link** or **Private Service Connect** techn > **Note:** > -> A private endpoint is a project-level resource and is not tied to a specific cluster. Private endpoints created within the same project can be shared by multiple 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. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any cluster. +> 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 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. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any cluster.
From ae0ae783dab2ab76ae836083088015ef35030250 Mon Sep 17 00:00:00 2001 From: Ginkgoch Date: Fri, 28 Aug 2026 10:46:07 +0800 Subject: [PATCH 3/5] Apply suggestion from @qiancai Co-authored-by: Grace Cai --- tidb-cloud/premium/set-up-sink-private-endpoint-premium.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md b/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md index 8307673b32566..5426d2b1e7835 100644 --- a/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md +++ b/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md @@ -27,7 +27,7 @@ Private endpoints leverage the **Private Link** technology from cloud providers, > **Note:** > -> A private endpoint is a tenant-level resource and is not tied to a specific instance. Private endpoints created within the same tenant 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 an instance does not delete its private endpoints. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any instance. +> 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. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any instance.
From e6bdaccdb7d8b17569ef8dbb3bdb97613f88f771 Mon Sep 17 00:00:00 2001 From: Ginkgoch Date: Fri, 28 Aug 2026 15:19:14 +0800 Subject: [PATCH 4/5] Apply suggestion from @qiancai Co-authored-by: Grace Cai --- tidb-cloud/premium/set-up-sink-private-endpoint-premium.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md b/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md index 5426d2b1e7835..21d92a0b12213 100644 --- a/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md +++ b/tidb-cloud/premium/set-up-sink-private-endpoint-premium.md @@ -27,7 +27,8 @@ Private endpoints leverage the **Private Link** technology from cloud providers, > **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. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any instance. +> - 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.
From a567b7d5634e0d5fbb64f15ec7aed3cd8f6abdb1 Mon Sep 17 00:00:00 2001 From: Ginkgoch Date: Fri, 28 Aug 2026 15:19:24 +0800 Subject: [PATCH 5/5] Apply suggestion from @qiancai Co-authored-by: Grace Cai --- tidb-cloud/set-up-sink-private-endpoint.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tidb-cloud/set-up-sink-private-endpoint.md b/tidb-cloud/set-up-sink-private-endpoint.md index 340c3ffd7e495..480a8eaa785a5 100644 --- a/tidb-cloud/set-up-sink-private-endpoint.md +++ b/tidb-cloud/set-up-sink-private-endpoint.md @@ -32,7 +32,8 @@ Private endpoints leverage **Private Link** or **Private Service Connect** techn > **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 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. You can manually delete a private endpoint when it is no longer needed, or wait for it to be automatically cleaned up after 30 days of inactivity. A private endpoint cannot be deleted if it is still in use by any cluster. +> - 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.