pingcap · ginkgoch · Aug 26, 2026 · Aug 27, 2026 · Aug 28, 2026 · qiancai
diff --git 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 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. 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.
-> 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.
+
 <SimpleTab>
 <div label="AWS">
 

diff --git 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 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 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.
-> 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.
+
 <SimpleTab>
 <div label="AWS">