From fc9b6c259e9ab8cb420584fbdeee8be5ac5292b2 Mon Sep 17 00:00:00 2001 From: Yanjie She <57549981+sheyanjie-qq@users.noreply.github.com> Date: Mon, 26 Jun 2023 09:27:34 +0800 Subject: [PATCH] Update docs/en/14-network/private-link/index.md Co-authored-by: WANG Xu --- docs/en/14-network/private-link/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/14-network/private-link/index.md b/docs/en/14-network/private-link/index.md index 0b9db0e168..3b63041586 100644 --- a/docs/en/14-network/private-link/index.md +++ b/docs/en/14-network/private-link/index.md @@ -7,7 +7,7 @@ description: This document describes how to connect your VPC to TDengine service ## Introduction PrivateLink is a highly available, scalable technology that you can use to privately connect your VPC to TDengine service as if they were in one VPC. PrivateLink allows the resources in your VPC to connect to TDengine service using your private IP addresses, and does not expose your data to the public internet. -Currently, TDengine Cloud only supports private endpoint connections in AWS. Other clouds similar to GCP or Azure will soon be supported. +Currently, TDengine Cloud only supports private endpoint connections in AWS. Other clouds such as GCP or Azure will soon be supported. The architecture of the PrivateLink is as follows: -- GitLab