Skip to content

Commit 2bd7ff7

Browse files
author
Docsite Preview Bot
committed
Sync files for PR pingcap/docs#22192 (commit: pingcap/docs@b272a54)
1 parent 1657523 commit 2bd7ff7

5 files changed

+17
-17
lines changed

markdown-pages/en/tidbcloud/master/TOC-tidb-cloud-essential.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -666,7 +666,7 @@
666666
- [TiDB Cloud Partners](/tidb-cloud/tidb-cloud-partners.md)
667667
- [MSP Customer](/tidb-cloud/managed-service-provider-customer.md)
668668
- [Reseller's Customer](/tidb-cloud/cppo-customer.md)
669-
- [TiDB Cloud Starter and Essential Limitations](/tidb-cloud/serverless-limitations.md)
669+
- [{{{ .starter }}} and Essential Limitations](/tidb-cloud/serverless-limitations.md)
670670
- [Limited SQL Features on TiDB Cloud](/tidb-cloud/limited-sql-features.md)
671671
- [TiDB Limitations](/tidb-limitations.md)
672672
- [System Variables](/system-variables.md)

markdown-pages/en/tidbcloud/master/tidb-cloud/serverless-private-link-connection-to-alicloud-rds.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ summary: Learn how to connect to an Alibaba Cloud ApsaraDB RDS for MySQL instanc
55

66
# Connect to Alibaba Cloud ApsaraDB RDS for MySQL via a Private Link Connection
77

8-
This document describes how to connect a TiDB Cloud Essential cluster to an [Alibaba Cloud ApsaraDB RDS for MySQL](https://www.alibabacloud.com/en/product/apsaradb-for-rds-mysql) instance using an Alibaba Cloud Endpoint Service private link connection.
8+
This document describes how to connect a {{{ .essential }}} cluster to an [Alibaba Cloud ApsaraDB RDS for MySQL](https://www.alibabacloud.com/en/product/apsaradb-for-rds-mysql) instance using an Alibaba Cloud Endpoint Service private link connection.
99

1010
## Prerequisites
1111

@@ -16,7 +16,7 @@ This document describes how to connect a TiDB Cloud Essential cluster to an [Ali
1616
- Manage load balancer
1717
- Manage endpoint services
1818

19-
- Your TiDB Cloud Essential cluster is on Alibaba Cloud, and it is active. Retrieve and save the following details for later use:
19+
- Your {{{ .essential }}} cluster is on Alibaba Cloud, and it is active. Retrieve and save the following details for later use:
2020

2121
- Account ID
2222
- Availability Zones (AZ)
@@ -33,8 +33,8 @@ Identify an Alibaba Cloud ApsaraDB RDS for MySQL that you want to use, or [creat
3333

3434
Your ApsaraDB RDS for MySQL instance must meet the following requirements:
3535

36-
- Region match: the instance must reside in the same Alibaba Cloud region as your TiDB Cloud Essential cluster.
37-
- AZ (Availability Zone) availability: the availability zones must overlap with those of your TiDB Cloud Essential cluster.
36+
- Region match: the instance must reside in the same Alibaba Cloud region as your {{{ .essential }}} cluster.
37+
- AZ (Availability Zone) availability: the availability zones must overlap with those of your {{{ .essential }}} cluster.
3838
- Network accessibility: the instance must be configured with proper IP whitelist and be accessible within the VPC.
3939

4040
> **Note**
@@ -63,7 +63,7 @@ Set up the load balancer in the same region of your ApsaraDB RDS for MySQL as fo
6363

6464
- **Network Type**: select `Internal-facing`
6565
- **VPC**: select the VPC where your ApsaraDB RDS for MySQL is located
66-
- **Zone**: it must overlap with your TiDB Cloud Essential cluster
66+
- **Zone**: it must overlap with your {{{ .essential }}} cluster
6767
- **IP Version**: select `IPv4`
6868

6969
4. Find the load balancer you created, and then click **Create Listener**. Provide the following information:

markdown-pages/en/tidbcloud/master/tidb-cloud/serverless-private-link-connection-to-aws-rds.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ summary: Learn how to connect to an Amazon RDS instance using an AWS Endpoint Se
55

66
# Connect to Amazon RDS via a Private Link Connection
77

8-
This document describes how to connect a TiDB Cloud Essential cluster to an [Amazon RDS](https://aws.amazon.com/rds/) instance using an AWS Endpoint Service private link connection.
8+
This document describes how to connect a {{{ .essential }}} cluster to an [Amazon RDS](https://aws.amazon.com/rds/) instance using an AWS Endpoint Service private link connection.
99

1010
## Prerequisites
1111

@@ -17,7 +17,7 @@ This document describes how to connect a TiDB Cloud Essential cluster to an [Ama
1717
- Manage load balancer
1818
- Manage endpoint services
1919

20-
- Your TiDB Cloud Essential is hosted on AWS, and it is active. Retrieve and save the following details for later use:
20+
- Your {{{ .essential }}} is hosted on AWS, and it is active. Retrieve and save the following details for later use:
2121

2222
- AWS Account ID
2323
- Availability Zones (AZ)
@@ -34,8 +34,8 @@ Identify an Amazon RDS instance to use, or [create a new one](https://docs.aws.a
3434

3535
The Amazon RDS instance must meet the following requirements:
3636

37-
- Region match: the instance must reside in the same AWS region as your TiDB Cloud Essential cluster.
38-
- The [subnet group](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Subnets) of your Amazon RDS instance must have overlapping availability zones as your TiDB Cloud Essential cluster.
37+
- Region match: the instance must reside in the same AWS region as your {{{ .essential }}} cluster.
38+
- The [subnet group](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Subnets) of your Amazon RDS instance must have overlapping availability zones as your {{{ .essential }}} cluster.
3939
- Set your Amazon RDS instance with a proper security group, and it is accessible within the VPC. For example, you can create a security group with the following rules:
4040

4141
- An inbound rule that allows MySQL/Aurora:
@@ -66,14 +66,14 @@ To set up the load balancer in the same region of your RDS, take the following s
6666
- **VPC**: the VPC where your RDS is located
6767
- **Register targets**: register the IP addresses of your Amazon RDS instance. You can ping the RDS endpoint to get the IP address.
6868

69-
For more information, see [Create a target group for your Network Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-target-group.html).
69+
For more information, see [Create a target group for your Network Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-target-group.html).
7070

7171
2. Go to [Load balancers](https://console.aws.amazon.com/ec2/home#LoadBalancers) to create a network load balancer. Provide the following information:
7272

7373
- **Schema**: select `Internal`
7474
- **Load balancer IP address type**: select `IPv4`
7575
- **VPC**: the VPC where your RDS is located
76-
- **Availability Zones**: it must overlap with your TiDB Cloud Essential cluster
76+
- **Availability Zones**: it must overlap with your {{{ .essential }}} cluster
7777
- **Security groups**: create a new security group with the following rules:
7878
- An inbound rule that allows MySQL/Aurora:
7979
- Type: `MySQL/Aurora`
@@ -86,8 +86,8 @@ To set up the load balancer in the same region of your RDS, take the following s
8686
- **Listeners and routing**:
8787
- **Protocol and Port**: set the protocol to TCP and port to your database port, for example `3306` for MySQL
8888
- **Target group**: select the target group you that create in the previous step
89-
90-
For more information, see [Create a Network Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-network-load-balancer.html).
89+
90+
For more information, see [Create a Network Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-network-load-balancer.html).
9191

9292
### Step 2.2. Set up the AWS Endpoint Service
9393

markdown-pages/en/tidbcloud/master/tidb-cloud/serverless-private-link-connection-to-self-hosted-kafka-in-alicloud.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ For example, the port mapping is as follows:
3535
- Manage load balancer
3636
- Manage endpoint services
3737

38-
- TiDB Cloud Essential information: confirm that your TiDB Cloud Essential is active in Alibaba Cloud provider. Retrieve and save the following details for later use:
38+
- {{{ .essential }}} information: confirm that your {{{ .essential }}} is active in Alibaba Cloud provider. Retrieve and save the following details for later use:
3939

4040
- Account ID
4141
- Availability Zones (AZ)

markdown-pages/en/tidbcloud/master/tidb-cloud/serverless-private-link-connection-to-self-hosted-kafka-in-aws.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ summary: Learn how to connect to an AWS Self-Hosted Kafka using an AWS Endpoint
55

66
# Connect to AWS Self-Hosted Kafka via Private Link Connection
77

8-
This document describes how to connect a TiDB Cloud Essential cluster to a self-hosted Kafka cluster in AWS using AWS Endpoint Service [private link connection](/tidb-cloud/serverless-private-link-connection.md).
8+
This document describes how to connect a {{{ .essential }}} cluster to a self-hosted Kafka cluster in AWS using AWS Endpoint Service [private link connection](/tidb-cloud/serverless-private-link-connection.md).
99

1010
The mechanism works as follows:
1111

@@ -29,7 +29,7 @@ The mechanism works as follows:
2929
- Manage load balancer
3030
- Manage endpoint services
3131

32-
- Ensure that your TiDB Cloud Essential is active in AWS. Retrieve and save the following details for later use:
32+
- Ensure that your {{{ .essential }}} is active in AWS. Retrieve and save the following details for later use:
3333

3434
- Account ID
3535
- Availability Zones (AZs)

0 commit comments

Comments
 (0)