+
+
+To use the AWS CLI to create a VPC interface endpoint, perform the following steps:
+
+1. Copy the generated command and run it in your terminal.
+2. Record the VPC endpoint ID you just created.
+
+> **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.
+>
+> - If your service is spanning across more than three availability zones (AZs), you will get an error message indicating that the VPC endpoint service does not support the AZ of the subnet. This issue occurs when there is an extra AZ in your selected region in addition to the AZs where your TiDB instance is located. In this case, you can contact [PingCAP Technical Support](https://docs.pingcap.com/tidbcloud/tidb-cloud-support).
+
+
+
+
+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 [https://console.aws.amazon.com/vpc/](https://console.aws.amazon.com/vpc/).
+2. Click **Endpoints** in the navigation pane, and then click **Create Endpoint** in the upper-right corner.
+
+ The **Create endpoint** page is displayed.
+
+ 
+
+3. In the **Endpoint settings** area, fill in a name tag if needed, and then select the **Endpoint services that use NLBs and GWLBs** option.
+4. In the **Service settings** area, enter the service name `${your_endpoint_service_name}` from the generated command (`--service-name ${your_endpoint_service_name}`).
+5. Click **Verify service**.
+6. In the **Network settings** area, select your VPC in the drop-down list.
+7. In the **Subnets** area, select the availability zones where your TiDB instance is located.
+
+ > **Tip:**
+ >
+ > If your service is spanning across more than three availability zones (AZs), you might not be able to select AZs in the **Subnets** area. This issue occurs when there is an extra AZ in your selected region in addition to the AZs where your TiDB instance is located. In this case, contact [PingCAP Technical Support](https://docs.pingcap.com/tidbcloud/tidb-cloud-support).
+
+8. In the **Security groups** area, select your security group properly.
+
+ > **Note:**
+ >
+ > Make sure the selected security group allows inbound access from your EC2 instances on Port 4000 or a customer-defined port.
+
+9. Click **Create endpoint**.
+
+
+
+
+### Step 3. Create a private endpoint connection
+
+1. Go back to the TiDB Cloud console.
+2. On the **Create AWS Private Endpoint Connection** page, enter your VPC endpoint ID.
+3. Click **Create Private Endpoint Connection**.
+
+> **Tip:**
+>
+> You can view and manage private endpoint connections on your target TiDB instance, and then click **Settings** > **Networking** in the left navigation pane.
+
+### Step 4. Enable private DNS
+
+Enable private DNS in AWS. You can either use the AWS CLI or the AWS Management Console.
+
+
+
+
+To enable private DNS using your AWS CLI, copy the following `aws ec2 modify-vpc-endpoint` command from the **Create Private Endpoint Connection** page and run it in your AWS CLI.
+
+```bash
+aws ec2 modify-vpc-endpoint --vpc-endpoint-id ${your_vpc_endpoint_id} --private-dns-enabled
+```
+
+Alternatively, you can find the command on the **Networking** page of your instance. Locate the private endpoint and click **...*** > **Enable DNS** in the **Action** column.
+
+
+
+
+To enable private DNS in your AWS Management Console:
+
+1. Go to **VPC** > **Endpoints**.
+2. Right-click your endpoint ID and select **Modify private DNS name**.
+3. Select the **Enable for this endpoint** check box.
+4. Click **Save changes**.
+
+ 
+
+
+
+
+### Step 5. Connect to your TiDB instance
+
+After you have accepted the private endpoint connection, you are redirected back to the connection dialog.
+
+1. Wait for the private endpoint connection status to change from **System Checking** to **Active** (approximately 5 minutes).
+2. In the **Connect With** drop-down list, select your preferred connection method. The corresponding connection string is displayed at the bottom of the dialog.
+3. Connect to your instance with the connection string.
+
+> **Tip:**
+>
+> If you cannot connect to the instance, the reason might be that the security group of your VPC endpoint in AWS is not properly set. See [this FAQ](#troubleshooting) for solutions.
+
+### Private endpoint status reference
+
+When you use private endpoint connections, the statuses of private endpoints or private endpoint services is displayed on your instance-level **Networking** page:
+
+- switch to your target instance using the combo box in the upper-left corner, and then click **Settings** > **Networking** in the left navigation pane.
+
+The possible statuses of a private endpoint are explained as follows:
+
+- **Not Configured**: The endpoint service is created but the private endpoint is not created yet.
+- **Pending**: Waiting for processing.
+- **Active**: Your private endpoint is ready to use. You cannot edit a private endpoint in this status.
+- **Deleting**: The private endpoint is being deleted.
+- **Failed**: The private endpoint creation fails. You can click **Edit** of that row to retry the creation.
+
+The possible statuses of a private endpoint service are explained as follows:
+
+- **Creating**: The endpoint service is being created, which takes 3 to 5 minutes.
+- **Active**: The endpoint service is created, regardless of whether the private endpoint is created or not.
+- **Deleting**: The endpoint service or the instance is being deleted, which takes 3 to 5 minutes.
+
+## Troubleshooting
+
+### I cannot connect to a TiDB instance 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.
+
+