+ You can get the following connection parameters `${tidb_endpoint}`, `${port}`, and `${user}` from the connection string in the [**Connect**](/tidb-cloud/connect-via-standard-connection-serverless.md) dialog.
+
```shell
tiup dumpling -h ${tidb_endpoint} -P 4000 -u ${user} -p ${password} -F 67108864MiB -t 4 -o ${export_dir} --filetype sql --consistency none
```
@@ -58,6 +58,8 @@ You can use the tool [Dumpling](/dumpling-overview.md) for data export.
+ You can get the following connection parameters `${tidb_endpoint}`, `${port}`, and `${user}` from the connection string in the [**Connect**](/tidb-cloud/connect-via-standard-connection.md) dialog.
+
```shell
tiup dumpling:v6.5.2 -h ${tidb_endpoint} -P ${port} -u ${user} -p ${password} -F 67108864MiB -t 4 -o ${export_dir} --filetype sql
```
diff --git a/tidb-cloud/index-insight.md b/tidb-cloud/index-insight.md
index 29197e86100e9..5557e1e51f107 100644
--- a/tidb-cloud/index-insight.md
+++ b/tidb-cloud/index-insight.md
@@ -26,7 +26,7 @@ This section introduces how to enable the Index Insight feature and obtain recom
### Before you begin
-Before enabling the Index Insight feature, make sure that you have created a TiDB Dedicated cluster. If you do not have one, follow the steps in [Create a cluster](/tidb-cloud/create-tidb-cluster.md) to create one.
+Before enabling the Index Insight feature, make sure that you have created a TiDB Dedicated cluster. If you do not have one, follow the steps in [Create a TiDB Dedicated cluster](/tidb-cloud/create-tidb-cluster.md) to create one.
### Step 1: Enable Index Insight
@@ -46,7 +46,7 @@ Before enabling the Index Insight feature, make sure that you have created a TiD
> **Note:**
>
- > To connect to your TiDB Dedicated cluster, see [Connect to a TiDB cluster](/tidb-cloud/connect-to-tidb-cluster.md).
+ > To connect to your TiDB Dedicated cluster, see [Connect to a TiDB Dedicated cluster](/tidb-cloud/connect-to-tidb-cluster.md).
4. Enter the username and password of the SQL user created in the preceding step. Then, click **Activate** to initiate the activation process.
diff --git a/tidb-cloud/integrate-tidbcloud-with-airbyte.md b/tidb-cloud/integrate-tidbcloud-with-airbyte.md
index d1ec06d29f54f..13860d51f29a5 100644
--- a/tidb-cloud/integrate-tidbcloud-with-airbyte.md
+++ b/tidb-cloud/integrate-tidbcloud-with-airbyte.md
@@ -46,7 +46,7 @@ Conveniently, the steps are the same for setting TiDB as the source and the dest
1. Click **Sources** or **Destinations** in the sidebar and choose TiDB type to create a new TiDB connector.
-2. Fill in the following parameters. See [Connect via standard connection](/tidb-cloud/connect-via-standard-connection.md) to get the connection information from the connection string.
+2. Fill in the following parameters.
- Host: The endpoint of your TiDB Cloud cluster
- Port: The port of the database
@@ -54,6 +54,8 @@ Conveniently, the steps are the same for setting TiDB as the source and the dest
- Username: The username to access the database
- Password: The password of the username
+ You can get the parameter values from the connection dialog of your cluster. To open the dialog, click the ☰ hover menu in the upper-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner.
+
3. Enable **SSL Connection**, and set TLS protocols to **TLSv1.2** or **TLSv1.3** in **JDBC URL Params**.
> Note:
diff --git a/tidb-cloud/integrate-tidbcloud-with-dbt.md b/tidb-cloud/integrate-tidbcloud-with-dbt.md
index 3946c22a39339..8f17611e79ae3 100644
--- a/tidb-cloud/integrate-tidbcloud-with-dbt.md
+++ b/tidb-cloud/integrate-tidbcloud-with-dbt.md
@@ -90,7 +90,7 @@ To configure the project, take the following steps:
password: "your_password" # The password to use for authenticating to the TiDB Cloud clusters
```
- You can get the values of `server`, `port`, and `username` from the [**Connect**](/tidb-cloud/connect-via-standard-connection.md) dialog in TiDB Cloud console.
+ You can get the values of `server`, `port`, and `username` from the connection dialog of your cluster. To open this dialog, click the ☰ hover menu in the upper-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner.
2. Complete the project configuration.
diff --git a/tidb-cloud/integrate-tidbcloud-with-netlify.md b/tidb-cloud/integrate-tidbcloud-with-netlify.md
index 22d63b8feb81e..60314a8090082 100644
--- a/tidb-cloud/integrate-tidbcloud-with-netlify.md
+++ b/tidb-cloud/integrate-tidbcloud-with-netlify.md
@@ -22,7 +22,10 @@ You are expected to have a Netlify account and CLI. If you do not have any, refe
### A TiDB Cloud account and a TiDB cluster
-You are expected to have an account and a cluster in TiDB Cloud. If you do not have any, refer to [Create a TiDB cluster](/tidb-cloud/create-tidb-cluster.md).
+You are expected to have an account and a cluster in TiDB Cloud. If you do not have any, refer to the following to create one:
+
+- [Create a TiDB Serverless cluster](/tidb-cloud/create-tidb-cluster-serverless.md)
+- [Create a TiDB Dedicated cluster](/tidb-cloud/create-tidb-cluster.md)
One TiDB Cloud cluster can connect to multiple Netlify sites.
@@ -96,7 +99,7 @@ For a TiDB Dedicated cluster, you can get the connection string only from the Ti
-1. Navigate to the [TiDB Cloud console](https://tidbcloud.com/), and get the following connection parameters from the connection string in the [**Connect**](/tidb-cloud/connect-via-standard-connection.md) dialog.
+1. In the [TiDB Cloud console](https://tidbcloud.com/), click the ☰ hover menu in the upper-left corner, click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner. In the displayed dialog, you can get the following connection parameters from the connection string.
- `${host}`
- `${port}`
diff --git a/tidb-cloud/integrate-tidbcloud-with-vercel.md b/tidb-cloud/integrate-tidbcloud-with-vercel.md
index 8b041351ee60b..bff6e23dca2d2 100644
--- a/tidb-cloud/integrate-tidbcloud-with-vercel.md
+++ b/tidb-cloud/integrate-tidbcloud-with-vercel.md
@@ -31,7 +31,10 @@ One Vercel project can only connect to one TiDB Cloud cluster. To change the int
### A TiDB Cloud account and a TiDB cluster
-You are expected to have an account and a cluster in TiDB Cloud. If you do not have any, refer to [Create a TiDB cluster](/tidb-cloud/create-tidb-cluster.md).
+You are expected to have an account and a cluster in TiDB Cloud. If you do not have any, refer to the following to create one:
+
+- [Create a TiDB Serverless cluster](/tidb-cloud/create-tidb-cluster-serverless.md)
+- [Create a TiDB Dedicated cluster](/tidb-cloud/create-tidb-cluster.md)
To [integrate with Vercel via the TiDB Cloud Vercel Integration](#connect-via-the-tidb-cloud-vercel-integration), you are expected to have the "Owner" access to your organization or the "Member" access to the target project in TiDB Cloud. For more information, see [Manage role access](/tidb-cloud/manage-user-access.md#manage-role-access).
@@ -88,7 +91,9 @@ DATABASE_URL
## Connect via manually setting environment variables
-1. Follow the steps in [Connect to a TiDB Cloud cluster via standard connection](/tidb-cloud/connect-via-standard-connection.md) to get the connection information of your TiDB cluster.
+1. Get the connection information of your TiDB cluster.
+
+ You can get the connection information from the connection dialog of your cluster. To open the dialog, click the ☰ hover menu in the upper-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner.
> **Note:**
>
diff --git a/tidb-cloud/manage-serverless-spend-limit.md b/tidb-cloud/manage-serverless-spend-limit.md
index 92a9b88ea86c7..ea385e31ac05a 100644
--- a/tidb-cloud/manage-serverless-spend-limit.md
+++ b/tidb-cloud/manage-serverless-spend-limit.md
@@ -24,7 +24,7 @@ Once the free quota of a cluster is reached, the read and write operations on th
To learn more about the RU consumption of different resources (including read, write, SQL CPU, and network egress), the pricing details, and the throttled information, see [TiDB Serverless Pricing Details](https://www.pingcap.com/tidb-cloud-serverless-pricing-details).
-If you want to create a TiDB Serverless cluster with an additional quota, you can edit the spend limit on the cluster creation page. For more information, see [Create a TiDB cluster](/tidb-cloud/create-tidb-cluster.md#step-4-create-a-tidb-cluster).
+If you want to create a TiDB Serverless cluster with an additional quota, you can edit the spend limit on the cluster creation page. For more information, see [Create a TiDB Serverless cluster](/tidb-cloud/create-tidb-cluster-serverless.md).
## Update spend limit
diff --git a/tidb-cloud/migrate-from-mysql-using-data-migration.md b/tidb-cloud/migrate-from-mysql-using-data-migration.md
index cbb9012705d97..e9423824153bb 100644
--- a/tidb-cloud/migrate-from-mysql-using-data-migration.md
+++ b/tidb-cloud/migrate-from-mysql-using-data-migration.md
@@ -104,11 +104,11 @@ To quickly test a migration job, you can use the `root` account of the TiDB Clou
### Set up network connection
-Before creating a migration job, set up the network connection according to your connection methods. See [Connect to Your TiDB Cluster](/tidb-cloud/connect-to-tidb-cluster.md).
+Before creating a migration job, set up the network connection according to your connection methods. See [Connect to Your TiDB Dedicated Cluster](/tidb-cloud/connect-to-tidb-cluster.md).
- If you use public IP (this is, standard connection) for network connection, make sure that the upstream database can be connected through the public network.
-- If you use AWS PrivateLink, set it up according to [Set Up Private Endpoint Connections](/tidb-cloud/set-up-private-endpoint-connections.md).
+- If you use AWS PrivateLink, set it up according to [Connect to TiDB Dedicated via Private Endpoint](/tidb-cloud/set-up-private-endpoint-connections.md).
- If you use AWS VPC Peering or GCP VPC Network Peering, see the following instructions to configure the network.
diff --git a/tidb-cloud/pause-or-resume-tidb-cluster.md b/tidb-cloud/pause-or-resume-tidb-cluster.md
index b31f770411dc5..c5cee33aba3b7 100644
--- a/tidb-cloud/pause-or-resume-tidb-cluster.md
+++ b/tidb-cloud/pause-or-resume-tidb-cluster.md
@@ -1,11 +1,11 @@
---
-title: Pause or Resume a TiDB Cluster
-summary: Learn how to pause or resume a TiDB cluster.
+title: Pause or Resume a TiDB Dedicated Cluster
+summary: Learn how to pause or resume a TiDB Dedicated cluster.
---
-# Pause or Resume a TiDB Cluster
+# Pause or Resume a TiDB Dedicated Cluster
-You can easily pause and resume a cluster that is not in operation at all times in TiDB Cloud.
+You can easily pause and resume a TiDB Dedicated cluster that is not in operation at all times in TiDB Cloud.
The pause does not affect your data stored in the cluster but only stops the collection of monitoring information and the consumption of computing resources. After the pause, you can resume your cluster at any time.
@@ -70,6 +70,6 @@ To resume a paused cluster, take the following steps:
3. In the dialog, click **Resume** to confirm your choice. The cluster status becomes **RESUMING**.
-Depending on your cluster size, it can take several minutes to resume the cluster. After the cluster is resumed, the cluster state changes from **RESUMING**to **AVAILABLE**.
+Depending on your cluster size, it can take several minutes to resume the cluster. After the cluster is resumed, the cluster state changes from **RESUMING** to **AVAILABLE**.
You can also resume a cluster using TiDB Cloud API. Currently, TiDB Cloud API is still in beta. For more information, see [TiDB Cloud API Documentation](https://docs.pingcap.com/tidbcloud/api/v1beta).
diff --git a/tidb-cloud/release-notes-2022.md b/tidb-cloud/release-notes-2022.md
index 7ca10c3e6ae00..972e344b54c3e 100644
--- a/tidb-cloud/release-notes-2022.md
+++ b/tidb-cloud/release-notes-2022.md
@@ -92,7 +92,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c
- Introduce the left navigation bar to maximize screen usage efficiency.
- Adopt a flatter navigation hierarchy.
-- Improve the [**Connect**](/tidb-cloud/connect-to-tidb-cluster.md) experience for Serverless Tier users.
+- Improve the [**Connect**](/tidb-cloud/connect-to-tidb-cluster-serverless.md) experience for Serverless Tier users.
Now developers can connect to SQL editor or with their preferred tools in just a few clicks without context switching.
diff --git a/tidb-cloud/serverless-tier-limitations.md b/tidb-cloud/serverless-tier-limitations.md
index d3fff1b7c2348..90f4214cbd9b4 100644
--- a/tidb-cloud/serverless-tier-limitations.md
+++ b/tidb-cloud/serverless-tier-limitations.md
@@ -29,7 +29,7 @@ We are constantly filling in the feature gaps between TiDB Serverless and TiDB D
### Connection
-- Only [Standard Connection](/tidb-cloud/connect-via-standard-connection.md) and [Private Endpoint](/tidb-cloud/set-up-private-endpoint-connections.md) can be used. You cannot use [VPC Peering](/tidb-cloud/set-up-vpc-peering-connections.md) to connect to TiDB Serverless clusters.
+- Only [Standard Connection](/tidb-cloud/connect-via-standard-connection-serverless.md) and [Private Endpoint](/tidb-cloud/set-up-private-endpoint-connections-serverless.md) can be used. You cannot use [VPC Peering](/tidb-cloud/set-up-vpc-peering-connections.md) to connect to TiDB Serverless clusters.
- No "IP Access List" support.
### Monitoring
@@ -66,6 +66,6 @@ Once the free quota of a cluster is reached, the read and write operations on th
To learn more about the RU consumption of different resources (including read, write, SQL CPU, and network egress), the pricing details, and the throttled information, see [TiDB Serverless Pricing Details](https://www.pingcap.com/tidb-cloud-serverless-pricing-details).
-If you want to create a TiDB Serverless cluster with an additional quota, you can edit the spend limit on the cluster creation page. For more information, see [Create a TiDB cluster](/tidb-cloud/create-tidb-cluster.md#step-4-create-a-tidb-cluster).
+If you want to create a TiDB Serverless cluster with an additional quota, you can edit the spend limit on the cluster creation page. For more information, see [Create a TiDB Serverless cluster](/tidb-cloud/create-tidb-cluster-serverless.md).
After creating a TiDB Serverless, you can still check and edit the spend limit on your cluster overview page. For more information, see [Manage Spend Limit for TiDB Serverless Clusters](/tidb-cloud/manage-serverless-spend-limit.md).
diff --git a/tidb-cloud/set-up-private-endpoint-connections-serverless.md b/tidb-cloud/set-up-private-endpoint-connections-serverless.md
new file mode 100644
index 0000000000000..293bc3d7c8a29
--- /dev/null
+++ b/tidb-cloud/set-up-private-endpoint-connections-serverless.md
@@ -0,0 +1,125 @@
+---
+title: Connect to TiDB Serverless via Private Endpoint
+summary: Learn how to connect to your TiDB Cloud cluster via private endpoint.
+---
+
+# Connect to TiDB Serverless via Private Endpoint
+
+This document describes how to connect to your TiDB Serverless cluster via private endpoint.
+
+> **Tip:**
+>
+> To learn how to connect to a TiDB Dedicated cluster via private endpoint, see [Connect to TiDB Dedicated via Private Endpoint](/tidb-cloud/set-up-private-endpoint-connections.md).
+
+TiDB Cloud supports highly secure and one-way access to the TiDB Cloud service hosted in an AWS VPC via the [AWS PrivateLink](https://aws.amazon.com/privatelink/?privatelink-blogs.sort-by=item.additionalFields.createdDate&privatelink-blogs.sort-order=desc), as if the service were in your own VPC. A private endpoint is exposed in your VPC and you can create a connection to the TiDB Cloud service via the endpoint with permission.
+
+Powered by AWS PrivateLink, the endpoint connection is secure and private, and does not expose your data to the public internet. In addition, the endpoint connection supports CIDR overlap and is easier for network management.
+
+The architecture of the private endpoint is as follows:
+
+
+
+For more detailed definitions of the private endpoint and endpoint service, see the following AWS documents:
+
+- [What is AWS PrivateLink?](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html)
+- [AWS PrivateLink concepts](https://docs.aws.amazon.com/vpc/latest/privatelink/concepts.html)
+
+## Restrictions
+
+- Currently, TiDB Cloud supports private endpoint connection only when the endpoint service is hosted in AWS. If the service is hosted in Google Cloud Platform (GCP), the private endpoint is not applicable.
+- Private endpoint connection across regions is not supported.
+
+## Set up a private endpoint with AWS
+
+To connect to your TiDB Serverless cluster via a private endpoint, follow these steps:
+
+1. [Choose a TiDB cluster](#step-1-choose-a-tidb-cluster)
+2. [Create an AWS interface endpoint](#step-2-create-an-aws-interface-endpoint)
+3. [Connect to your TiDB cluster](#step-3-connect-to-your-tidb-cluster)
+
+### Step 1. Choose a TiDB cluster
+
+1. On the [**Clusters**](https://tidbcloud.com/console/clusters) page, click the name of your target TiDB Serverless cluster to go to its overview page.
+2. Click **Connect** in the upper-right corner. A connection dialog is displayed.
+3. In the **Endpoint Type** drop-down list, select **Private**.
+4. Take a note of **Service Name**, **Availability Zone ID**, and **Region ID**.
+
+ > **Note:**
+ >
+ > You only need to create one private endpoint per AWS region, which can be shared by all TiDB Serverless clusters located in the same region.
+
+### Step 2. Create an AWS interface endpoint
+
+
+
+
+To use the AWS Management Console to create a VPC interface endpoint, perform the following steps:
+
+1. Sign in to the [AWS Management Console](https://aws.amazon.com/console/) and open the Amazon VPC console at .
+2. Click **Endpoints** in the navigation pane, and then click **Create Endpoint** in the upper-right corner.
+
+ The **Create endpoint** page is displayed.
+
+ 
+
+3. Select **Other endpoint services**.
+4. Enter the service name that you found in [step 1](#step-1-choose-a-tidb-cluster).
+5. Click **Verify service**.
+6. Select your VPC in the drop-down list. Expand **Additional settings** and select the **Enable DNS name** checkbox.
+7. In the **Subnets** area, select the availability zone where your TiDB cluster is located, and select the Subnet ID.
+8. Select your security group properly in the **Security groups** area.
+
+ > **Note:**
+ >
+ > Make sure the selected security group allows inbound access from your EC2 instances on port 4000.
+
+9. Click **Create endpoint**.
+
+
+
+
+To use the AWS CLI to create a VPC interface endpoint, perform the following steps:
+
+1. To get the **VPC ID** and **Subnet ID**, navigate to your AWS Management Console, and locate them in the relevant sections. Make sure that you fill in the **Availability Zone ID** that you found in [step 1](#step-1-choose-a-tidb-cluster).
+2. Copy the command provided below, replace the relevant arguments with the information you obtained, and then execute it in your terminal.
+
+```bash
+aws ec2 create-vpc-endpoint --vpc-id ${your_vpc_id} --region ${region_id} --service-name ${service_name} --vpc-endpoint-type Interface --subnet-ids ${your_subnet_id}
+```
+
+> **Tip:**
+>
+> Before running the command, you need to have AWS CLI installed and configured. See [AWS CLI configuration basics](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html) for details.
+
+
+
+
+Then you can connect to the endpoint service with the private DNS name.
+
+### Step 3: Connect to your TiDB cluster
+
+After you have created the interface endpoint, go back to the TiDB Cloud console and take the following steps:
+
+1. On the [**Clusters**](https://tidbcloud.com/console/clusters) page, click the name of your target cluster to go to its overview page.
+2. Click **Connect** in the upper-right corner. A connection dialog is displayed.
+3. In the **Endpoint Type** drop-down list, select **Private**.
+4. In the **Connect With** drop-down list, select your preferred connection method. The corresponding connection string is displayed at the bottom of the dialog.
+5. Connect to your cluster with the connection string.
+
+> **Tip:**
+>
+> If you cannot connect to the cluster, 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.
+
+## Troubleshooting
+
+### I cannot connect to a TiDB cluster via a private endpoint after enabling private DNS. Why?
+
+You might need to properly set the security group for your VPC endpoint in the AWS Management Console. Go to **VPC** > **Endpoints**. Right-click your VPC endpoint and select the proper **Manage security groups**. A proper security group within your VPC that allows inbound access from your EC2 instances on Port 4000 or a customer-defined port.
+
+
+
+### I cannot enable private DNS. An error is reported indicating that the `enableDnsSupport` and `enableDnsHostnames` VPC attributes are not enabled
+
+Make sure that DNS hostname and DNS resolution are both enabled in your VPC setting. They are disabled by default when you create a VPC in the AWS Management Console.
diff --git a/tidb-cloud/set-up-private-endpoint-connections.md b/tidb-cloud/set-up-private-endpoint-connections.md
index 1460056542958..81f025f18e22c 100644
--- a/tidb-cloud/set-up-private-endpoint-connections.md
+++ b/tidb-cloud/set-up-private-endpoint-connections.md
@@ -1,9 +1,15 @@
---
-title: Connect via Private Endpoint
+title: Connect to TiDB Dedicated via Private Endpoint
summary: Learn how to connect to your TiDB Cloud cluster via private endpoint.
---
-# Connect via Private Endpoint
+# Connect to TiDB Dedicated via Private Endpoint
+
+This document describes how to connect to your TiDB Dedicated cluster via private endpoint.
+
+> **Tip:**
+>
+> To learn how to connect to a TiDB Serverless cluster via private endpoint, see [Connect to TiDB Serverless via Private Endpoint](/tidb-cloud/set-up-private-endpoint-connections-serverless.md).
TiDB Cloud supports highly secure and one-way access to the TiDB Cloud service hosted in an AWS VPC via the [AWS PrivateLink](https://aws.amazon.com/privatelink/?privatelink-blogs.sort-by=item.additionalFields.createdDate&privatelink-blogs.sort-order=desc), as if the service were in your own VPC. A private endpoint is exposed in your VPC and you can create a connection to the TiDB Cloud service via the endpoint with permission.
@@ -31,93 +37,6 @@ In most scenarios, you are recommended to use private endpoint connection over V
## Set up a private endpoint with AWS
-This section describes how to set up a private endpoint with AWS PrivateLink for a TiDB Serverless cluster and a TiDB Dedicated cluster.
-
-### TiDB Serverless
-
-To connect to your TiDB Serverless cluster via a private endpoint, follow these steps:
-
-1. [Choose a TiDB cluster](#step-1-choose-a-tidb-cluster)
-2. [Create an AWS interface endpoint](#step-2-create-an-aws-interface-endpoint)
-3. [Connect to your TiDB cluster](#step-3-connect-to-your-tidb-cluster)
-
-#### Step 1. Choose a TiDB cluster
-
-1. On the [**Clusters**](https://tidbcloud.com/console/clusters) page, click the name of your target TiDB Serverless cluster to go to its overview page.
-2. Click **Connect** in the upper-right corner. A connection dialog is displayed.
-3. In the **Endpoint Type** drop-down list, select **Private**.
-4. Take a note of **Service Name**, **Availability Zone ID**, and **Region ID**.
-
- > **Note:**
- >
- > You only need to create one private endpoint per AWS region, which can be shared by all TiDB Serverless clusters located in the same region.
-
-#### Step 2. Create an AWS interface endpoint
-
-
-
-
-To use the AWS Management Console to create a VPC interface endpoint, perform the following steps:
-
-1. Sign in to the [AWS Management Console](https://aws.amazon.com/console/) and open the Amazon VPC console at .
-2. Click **Endpoints** in the navigation pane, and then click **Create Endpoint** in the upper-right corner.
-
- The **Create endpoint** page is displayed.
-
- 
-
-3. Select **Other endpoint services**.
-4. Enter the service name that you found in [step 1](#step-1-choose-a-tidb-cluster).
-5. Click **Verify service**.
-6. Select your VPC in the drop-down list. Expand **Additional settings** and select the **Enable DNS name** checkbox.
-7. In the **Subnets** area, select the availability zone where your TiDB cluster is located, and select the Subnet ID.
-8. Select your security group properly in the **Security groups** area.
-
- > **Note:**
- >
- > Make sure the selected security group allows inbound access from your EC2 instances on port 4000.
-
-9. Click **Create endpoint**.
-
-
-
-
-To use the AWS CLI to create a VPC interface endpoint, perform the following steps:
-
-1. To get the **VPC ID** and **Subnet ID**, navigate to your AWS Management Console, and locate them in the relevant sections. Make sure that you fill in the **Availability Zone ID** that you found in [step 1](#step-1-choose-a-tidb-cluster).
-2. Copy the command provided below, replace the relevant arguments with the information you obtained, and then execute it in your terminal.
-
-```bash
-aws ec2 create-vpc-endpoint --vpc-id ${your_vpc_id} --region ${region_id} --service-name ${service_name} --vpc-endpoint-type Interface --subnet-ids ${your_subnet_id}
-```
-
-> **Tip:**
->
-> Before running the command, you need to have AWS CLI installed and configured. See [AWS CLI configuration basics](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html) for details.
-
-
-
-
-Then you can connect to the endpoint service with the private DNS name.
-
-#### Step 3: Connect to your TiDB cluster
-
-After you have created the interface endpoint, go back to the TiDB Cloud console and take the following steps:
-
-1. On the [**Clusters**](https://tidbcloud.com/console/clusters) page, click the name of your target cluster to go to its overview page.
-2. Click **Connect** in the upper-right corner. A connection dialog is displayed.
-3. In the **Endpoint Type** drop-down list, select **Private**.
-4. In the **Connect With** drop-down list, select your preferred connection method. The corresponding connection string is displayed at the bottom of the dialog.
-5. Connect to your cluster with the connection string.
-
-> **Tip:**
->
-> If you cannot connect to the cluster, 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.
-
-### TiDB Dedicated
-
To connect to your TiDB Dedicated cluster via a private endpoint, complete the [prerequisites](#prerequisites) and follow these steps:
1. [Choose a TiDB cluster](#step-1-choose-a-tidb-cluster)
@@ -129,7 +48,7 @@ To connect to your TiDB Dedicated cluster via a private endpoint, complete the [
If you have multiple clusters, you need to repeat these steps for each cluster that you want to connect to using AWS PrivateLink.
-#### Prerequisites
+### Prerequisites
1. Log in to the [TiDB Cloud console](https://tidbcloud.com).
2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following:
@@ -140,12 +59,12 @@ If you have multiple clusters, you need to repeat these steps for each cluster t
3. Click the **Private Endpoint** tab.
4. Click **Add** in the upper-right corner.
-#### Step 1. Choose a TiDB cluster
+### Step 1. Choose a TiDB cluster
1. Click the drop-down list and choose an available TiDB Dedicated cluster.
2. Click **Next**.
-#### Step 2. Check the service endpoint region
+### Step 2. Check the service endpoint region
Your service endpoint region is selected by default. Have a quick check and click **Next**.
@@ -153,7 +72,7 @@ Your service endpoint region is selected by default. Have a quick check and clic
>
> The default region is where your cluster is located. Do not change it. Cross-region private endpoint is currently not supported.
-#### Step 3. Create an AWS interface endpoint
+### Step 3. Create an AWS interface endpoint
> **Note:**
>
@@ -216,13 +135,13 @@ To use the AWS CLI to create a VPC interface endpoint, perform the following ste