You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tidb-cloud/serverless-private-link-connection-to-alicloud-rds.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,20 +11,20 @@ This document describes how to connect to an Alibaba Cloud RDS instance using an
11
11
- Manage load balancer
12
12
- Manage endpoint services
13
13
14
-
3. Ensure your {{.essential}} in alibaba cloud provider and get its account ID and available zones, save the information for later use.
14
+
3. Ensure your {{{ .essential }}} in alibaba cloud provider and get its account ID and available zones, save the information for later use.
15
15
16
16
1. In the [TiDB Cloud console](https://tidbcloud.com), navigate to the cluster overview page of the TiDB cluster, and then click **Settings** > **Networking** in the left navigation pane.
17
17
2. On the **Private Link Connection For Dataflow**, click **Create Private Link Connection**.
18
-
3. You can find the AWS account ID and available zones information.
18
+
3. You can find the Alibaba Cloud account ID and available zones information.
19
19
20
20
## Step 1. Set up an RDS instance
21
21
22
22
Identify an Alibaba Cloud ApsaraDB RDS you want to use, or [set up a new RDS](https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/step-1-create-an-apsaradb-rds-for-mysql-instance-and-configure-databases).
23
23
24
24
The RDS must meet the following requirements:
25
25
26
-
- The Alibaba Cloud region for your RDS instance must be the same as the region for your {{.essential}}.
27
-
- The subnet group of your RDS must have overlapping availability zones as your {{.essential}}.
26
+
- The Alibaba Cloud region for your RDS instance must be the same as the region for your {{{ .essential }}}.
27
+
- The subnet group of your RDS must have overlapping availability zones as your {{{ .essential }}}.
28
28
- Make sure your RDS instance set proper IP whitelist and is accessible within the VPC.
29
29
30
30
> **Note**
@@ -49,7 +49,7 @@ Set up the load balancer in the same region of your RDS:
49
49
50
50
-**Network Type**: `Internal-facing`
51
51
-**VPC**: The VPC where your RDS is located
52
-
-**Zone**: Must have overlapping availability zones with your {{.essential}}
52
+
-**Zone**: Must have overlapping availability zones with your {{{ .essential }}}
53
53
-**IP Version**: `IPv4`
54
54
55
55
Find the load balancer you created, and then click **Create Listerner**:
Copy file name to clipboardExpand all lines: tidb-cloud/serverless-private-link-connection-to-aws-confluent.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ This document describes how to connect to an AWS Confluent Dedicated Cluster usi
10
10
11
11
1. You have a Confluent Cloud account.
12
12
13
-
2.Get the {{.essential}} account ID and available zones, save the information for later use.
13
+
2.Ensure your {{{ .essential }}} in aws provider and get the {{{ .essential }}} account ID and available zones, save the information for later use.
14
14
15
15
1. In the [TiDB Cloud console](https://tidbcloud.com), navigate to the cluster overview page of the TiDB cluster, and then click **Settings** > **Networking** in the left navigation pane.
16
16
2. On the **Private Link Connection For Dataflow**, click **Create Private Link Connection**.
@@ -22,16 +22,16 @@ Identify a Confluent Cloud network you want to use, or [set up a new Confluent C
22
22
23
23
The Confluent Cloud network must meet the following requirements:
24
24
25
-
- The network must be in the same AWS region as your {{.essential}}.
26
-
- The network must have overlapping availability zones as your {{.essential}}, recommended to have same availability zones.
25
+
- The network must be in the same AWS region as your {{{ .essential }}}.
26
+
- The network must have overlapping availability zones as your {{{ .essential }}}, recommended to have same availability zones.
27
27
28
28
On the `Network overview` page, obtain the `DNS subdomain` of the Confluent Cloud network. You need to extract the unique name from it.
29
29
For example, if the `DNS subdomain` is `use1-az1.domnprzqrog.us-east-1.aws.confluent.cloud`, then the unique name is `domnprzqrog.us-east-1`.
30
30
Please save the unique name for later use.
31
31
32
32
> **Note**
33
33
>
34
-
> The Confluent Cloud Dedicated cluster you want TiDB Cloud to connect to must be under this network.
34
+
> The Confluent Cloud Dedicated cluster you want TiDB Cloud to connect to must under this network.
35
35
36
36
## Step 2. Add a PrivateLink Access to the network
Copy file name to clipboardExpand all lines: tidb-cloud/serverless-private-link-connection-to-aws-rds.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ This document describes how to connect to an AWS RDS instance using an AWS Endpo
12
12
- Manage load balancer
13
13
- Manage endpoint services
14
14
15
-
3.Get the {{.essential}} account ID and available zones, save the information for later use.
15
+
3.Ensure your {{{ .essential }}} in aws provider and get the {{{ .essential }}} account ID and available zones, save the information for later use.
16
16
17
17
1. In the [TiDB Cloud console](https://tidbcloud.com), navigate to the cluster overview page of the TiDB cluster, and then click **Settings** > **Networking** in the left navigation pane.
18
18
2. On the **Private Link Connection For Dataflow**, Click **Create Private Link Connection**.
@@ -24,8 +24,8 @@ Identify an AWS RDS instance to use, or [set up a new one](https://docs.aws.amaz
24
24
25
25
The RDS must meet the following requirements:
26
26
27
-
- The RDS must be in the same AWS region as your {{.essential}}.
28
-
- The subnet group of your RDS must have overlapping availability zones as your {{.essential}}.
27
+
- The RDS must be in the same AWS region as your {{{ .essential }}}.
28
+
- The subnet group of your RDS must have overlapping availability zones as your {{{ .essential }}}.
29
29
- Make sure your RDS instance set proper security group and is accessible within the VPC.
30
30
31
31
> **Note**
@@ -53,7 +53,7 @@ Set up the load balancer in the same region of your RDS:
53
53
-**Schema**: `Internal`
54
54
-**Load balancer IP address type**: `IPv4`
55
55
-**VPC**: The VPC where your RDS is located
56
-
-**Availability Zones**: Must have overlapping availability zones with your {{.essential}}
56
+
-**Availability Zones**: Must have overlapping availability zones with your {{{ .essential }}}
57
57
-**Security groups**: Create a new security group with the following rules.
Copy file name to clipboardExpand all lines: tidb-cloud/serverless-private-link-connection-to-self-hosted-kafka-in-aws.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ The mechanism works as follows:
23
23
- Manage load balancer
24
24
- Manage endpoint services
25
25
26
-
3.Get the {{.essential}} account ID and available zones, save the information for later use.
26
+
3.Ensure your {{{ .essential }}} in aws provider and get the {{{ .essential }}} account ID and available zones, save the information for later use.
27
27
28
28
1. In the [TiDB Cloud console](https://tidbcloud.com), navigate to the cluster overview page of the TiDB cluster, and then click **Settings** > **Networking** in the left navigation pane.
29
29
2. On the **Private Link Connection For Dataflow**, click **Create Private Link Connection**.
### 2. Attach Domains to the Private Link Connection
748
748
749
749
You can also refer to [Attach Domains to a Private Link Connection](/tidbcloud/serverless-private-link-connection#attach-domains-to-a-private-link-connection) for more details.
750
750
@@ -763,7 +763,7 @@ You can also refer to [Attach Domains to a Private Link Connection](/tidbcloud/s
763
763
764
764
4. Click **Attach Domains**.
765
765
766
-
5. In the **Attach Domains** dialog, selectthe**TiDB Cloud Managed** domain type. The domains will be auto-generated by TiDB Cloud. Copy the unique name for later use and click **Attach Domains** to confirm.
766
+
5. In the **Attach Domains** dialog, selectthe**TiDB Cloud Managed** domain type. The domains will be auto-generated by TiDB Cloud. Copy the unique name for later use and click **Attach Domains** to confirm. For example, if the generated domain is `*.use1-az1.dvs6nl5jgveztmla3pxkxgh76i.aws.plc.tidbcloud.com`, then the unique name is `dvs6nl5jgveztmla3pxkxgh76i`.
## Step 4. Replace the Unique Name placeholder in Kafka configuration
788
788
789
-
1. Go back to your Kafka broker nodes, and replace the `unique_name` placeholder of each broker with the actual unique name you get from the previous step.
789
+
1. Go back to your Kafka broker nodes, replace the `unique_name` placeholderin`advertised.listeners` configuration of each broker with the actual unique name you get from the previous step.
790
790
2. After you reconfigure all the brokers, restart your Kafka brokers one by one.
Copy file name to clipboardExpand all lines: tidb-cloud/serverless-private-link-connection.md
+21-16Lines changed: 21 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,19 +12,19 @@ The Private Link Connection enables private, direct connectivity between {{{ .es
12
12
13
13
This type of private link connection enables TiDB Cloud clusters on **AWS** to connect to your [AWS endpoint service](https://docs.aws.amazon.com/vpc/latest/privatelink/create-endpoint-service.html) powered by AWS PrivateLink.
14
14
15
-
The Private Link Connection can access various AWS services by attach them to the endpoint service, including RDS instances and Kafka services, over a private network.
15
+
The Private Link Connection can access various AWS services by associating them to the endpoint service, such as RDS instances and Kafka services.
16
16
17
17
### AliCloud Endpoint Service
18
18
19
-
This type of private link connection enables TiDB Cloud clusters on **Alibaba Cloud** to connect to your [Alibaba Cloud endpoint service](https://www.alibabacloud.com/help/en/privatelink/share-your-service/) powered by Alibaba Cloud PrivateLink.
19
+
This type of private link connection enables TiDB Cloud clusters on **Alibaba Cloud** to connect to your [Alibaba Cloud endpoint service](https://www.alibabacloud.com/help/en/privatelink/share-your-service/#51976edba8no7) powered by Alibaba Cloud PrivateLink.
20
20
21
-
The Private Link Connection can access various Alibaba Cloud services by attaching them to the endpoint service, including RDS instances and Kafka services, over a private network.
21
+
The Private Link Connection can access various Alibaba Cloud services by associating them to the endpoint service, such as RDS instances and Kafka services.
22
22
23
23
## Attach Domains
24
24
25
25
You can attach domains to a private link connection.
26
26
27
-
When a domain is attached to the Private Link Connection, all traffic to this domain will be routed to this private link connection. It is useful when your service provides custom domains to clients at runtime, such as Kafka advertised listeners.
27
+
When a domain is attached to the private link connection, all traffic to this domain will be routed to this private link connection. It is useful when your service provides custom domains to clients at runtime, such as Kafka advertised listeners.
28
28
29
29
Different Private Link Connection types support attaching different domains:
30
30
@@ -61,11 +61,13 @@ You can manage Private Link Connections in the Console or via CLI.
61
61
-**Endpoint Service Name**: Enter your AWS endpoint service name (for example, `com.amazonaws.vpce.<region>.vpce-svc-xxxx`).
62
62
63
63
> **Note:**
64
-
>**Note:**
64
+
>
65
65
> Please make sure the AWS endpoint service:
66
-
> 1. Is in the same region as the TiDB Cloud cluster.
66
+
>
67
+
> 1. In the same region as your TiDB Cloud cluster.
67
68
> 2. Allows connections from the TiDB Cloud account.
68
-
> 3. Has availability zones that overlap with the TiDB Cloud cluster.
69
+
> 3. Has availability zones that overlap with your TiDB Cloud cluster.
70
+
>
69
71
> You can get the account ID and available zones information at the bottom of the dialog.
2. Has overlapping available zones of TiDB Cloud cluster.
85
+
1. In the same region of your TiDB Cloud cluster.
86
+
2. Allows the acceptance of TiDB Cloud account.
87
+
3. Has overlapping available zones of your TiDB Cloud cluster.
85
88
86
89
You can get the account ID and available zones information by the following command:
87
90
@@ -110,16 +113,18 @@ ticloud serverless private-link-connection zones --cluster-id <cluster-id>
110
113
4. Enter the required information in the **Create Private Link Connection** dialog:
111
114
112
115
-**Private Link Connection Name**: Enter a name for the Private Link Connection.
113
-
-**Connection Type**: Choose **AliCloud Endpoint Service**, if you can not find this option, please ensure that your cluster is created in Alibaba Cloud provider.
116
+
-**Connection Type**: Choose **AliCloud Endpoint Service**. If you can not find this option, please ensure that your cluster is created in Alibaba Cloud provider.
114
117
-**Endpoint Service Name**: Enter your Alibaba Cloud endpoint service name (for example, `com.aliyuncs.privatelink.<region>.xxxxx`).
115
118
116
119
> **Note:**
120
+
>
117
121
> Please make sure the Alibaba Cloud endpoint service:
118
-
> 1. Is in the same region as the TiDB Cloud cluster.
122
+
>
123
+
> 1. In the same region as your TiDB Cloud cluster.
119
124
> 2. Allows connections from the TiDB Cloud account.
120
-
> 3. Has availability zones that overlap with the TiDB Cloud cluster.
125
+
> 3. Has availability zones that overlap with your TiDB Cloud cluster.
126
+
>
121
127
> You can get the account ID and available zones information at the bottom of the dialog.
122
-
> You can get the account ID and available zones information in the button of the dialog.
0 commit comments