Rename VPC connection to PrivateLink (#2069)

* Update vpc-diagram.png

* Update vpc-diagram.png

* update

* Update PrivateLink-diagram.png

* update

* Update PrivateLink-create-a-connection.md

Author: WanYixian

cloud/PrivateLink-create-a-connection.md

@@ -0,0 +1,68 @@
+---
+id: PrivateLink-create-a-connection
+title: Create a PrivateLink connection
+description: Create a PrivateLink connection.
+slug: /create-a-connection
+---
+
+Follow the steps below to create a PrivateLink connection between RisingWave Cloud and your VPC.
+
+## Prerequisites
+
+- You need to create a cluster with the Pro plan or Enterprise plan in RisingWave Cloud:
+  
+  - See [Choose a cluster plan](/cluster-choose-a-cluster-plan.md) for more information. Please note that Developer clusters do not support PrivateLink connections.
+  
+  - The VPC you want to connect to and your cluster must be in the same region. If your preferred region is not available when creating a cluster, contact our [support team](mailto:cloud-support@risingwave-labs.com) or [sales team](mailto:sales@risingwave-labs.com).
+  
+- You need to set up a PrivateLink service in your VPC and make sure it runs properly. The following links might be helpful:
+  
+  - For AWS, see [Share your services through AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-share-your-services.html).
+  - For GCP, see [GCP Published services](https://cloud.google.com/vpc/docs/about-vpc-hosted-services).
+  - For Azure, see [Azure Private Link services](https://learn.microsoft.com/en-us/azure/private-link/private-link-service-overview).
+
+  :::note
+   Azure Private Link integration is currently in development and will be available soon.
+  :::
+
+## Steps
+
+1. Go to the [**PrivateLink**](https://cloud.risingwave.com/connection/) page and click **Create PrivateLink**.
+
+2. For **Platform**, select your cloud service provider. Currently, RisingWave Cloud supports **AWS** PrivateLink and **GCP** Private Service Connect.
+
+3. For **Cluster**, select the cluster you want to connect the VPC to. Ensure that the VPC and the cluster are in the same region.
+
+4. For **Name name**, enter a descriptive name for the connection.
+   
+5. For **Endpoint service name** or **Service attachment**:
+
+    <details><summary>If you choose AWS as the platform, enter the service name of the endpoint service.</summary>
+
+    You can find it in the [Amazon VPC console](https://console.aws.amazon.com/vpc/) → **Endpoint services** → **Service name** section.
+
+    <img
+    src={require('./images/aws-endpoint-service-name.png').default}
+    alt="AWS endpoint service name"
+    />
+
+    </details>
+
+    <details><summary>If you choose GCP as the platform, enter the server target URL of the service attachment.</summary> 
+
+    You can find it in the [Google Cloud Console](https://console.cloud.google.com/) → **Network services** → **Private Service Connect**.
+
+    <img
+    src={require('./images/gcp-service-attachment.png').default}
+    alt="GCP Service attachment"
+    />
+
+    </details>
+
+6. Click **Confirm** to create the connection.
+
+## What's next
+
+Now, you can create a source or sink with the PrivateLink connection using SQL.
+
+For details on how to use the VPC endpoint to create a source with the PrivateLink connection, see [Create source with PrivateLink connection](/docs/current/ingest-from-kafka/#create-source-with-privatelink-connection); for creating a sink, see [Create sink with PrivateLink connection](/docs/current/create-sink-kafka/#create-sink-with-privatelink-connection).

cloud/PrivateLink-drop-a-connection.md

@@ -0,0 +1,12 @@
+---
+id: PrivateLink-drop-a-connection
+title: Drop a PrivateLink connection
+description: If you no longer need to connect to a PrivateLink, you can drop the connection.
+slug: /drop-a-connection
+---
+
+Follow the steps below to drop a connection to your VPC when you no longer need it.
+
+1. Go to the [**Connection**](https://cloud.risingwave.com/connection/) page and click **Create PrivateLink**.
+
+2. Hover over the connection you want to drop and click the delete button, then confirm the deletion.

cloud/PrivateLink-overview.md

@@ -0,0 +1,63 @@
+---
+id: PrivateLink-overview
+title: PrivateLink connection
+description: Manage PrivateLink connections.
+slug: /PrivateLink-overview
+---
+
+## Concept
+
+In RisingWave Cloud, if you want to connect RisingWave clusters with your services inside your private Virtual Private Cloud (VPC) network, you can use the PrivateLink service to establish a private and secure connection between RisingWave Cloud and your private VPC in the same region.
+
+RisingWave Cloud utilizes the the private connection capability of the underlying Cloud vendors to establish the PrivateLink connection. In particular, the PrivateLink service is built on top of the following services:
+
+- [AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html)
+- [GCP Private Service Connect](https://cloud.google.com/vpc/docs/private-service-connect)
+- [Azure Private Link](https://learn.microsoft.com/en-us/azure/private-link/)
+
+:::note
+Azure Private Link integration is currently in development and will be available soon.
+:::
+
+The diagram below depicts a high-level overview of how PrivateLink service works. Both all three platforms share the same pattern of network structure so that you can configure them in the same way automatically.
+
+<img
+src={require('./images/PrivateLink-diagram.png').default}
+alt="VPC connection diagram"
+/>
+
+On the **RisingWave Cloud** side, RisingWave Cloud will create an endpoint (specifically an AWS VPC endpoint, GCP Private Service Connect endpoint, or Azure private endpoint) and bind it with one running RisingWave cluster.
+
+On the **Customer** side, you need to set up a PrivateLink service (specifically an AWS endpoint service, GCP published service, or Azure Private Link service) in your VPC network first.
+
+<grid
+ container
+ direction="row"
+ spacing="15"
+ justifyContent="space-between"
+ justifyItems="stretch"
+ alignItems="stretch">
+
+<grid item xs={12} sm={6} md={6}>
+
+<card
+title="Create a connection"
+content="Create a PrivateLink connection between RisingWave Cloud and your VPC."
+cloud="create-a-connection"
+style={{height: "80%"}}
+/>
+
+</grid>
+
+<grid item xs={12} sm={6} md={6}>
+
+<card
+title="Drop a connection"
+content="If you no longer need to connect to a VPC, you can drop the connection."
+cloud="drop-a-connection"
+style={{height: "80%"}}
+/>
+  
+</grid>
+
+</grid>

cloud/images/PrivateLink-diagram.png

@@ -214,11 +214,11 @@ FORMAT PLAIN ENCODE JSON;
 
 ```
 
-## Create sink with VPC connection
+## Create sink with PrivateLink connection
 
 If your Kafka sink service is located in a different VPC from RisingWave, use AWS PrivateLink or GCP Private Service Connect to establish a secure and direct connection. For details on how to set up an AWS PrivateLink connection, see [Create an AWS PrivateLink connection](/sql/commands/sql-create-connection.md#create-an-aws-privatelink-connection).
 
-To create a Kafka sink with a VPC connection, in the WITH section of your `CREATE SINK` statement, specify the following parameters.
+To create a Kafka sink with a PrivateLink connection, in the WITH section of your `CREATE SINK` statement, specify the following parameters.
 
 |Parameter| Notes|
 |---|---|

cloud/images/vpc-diagram.png

@@ -328,16 +328,16 @@ Based on the compatibility type that is configured for the schema registry, some
 
 To learn about compatibility types for Schema Registry and the changes allowed, see [Compatibility Types](https://docs.confluent.io/platform/current/schema-registry/avro.html#compatibility-types).
 
-## Create source with VPC connection
+## Create source with PrivateLink connection
 
 If your Kafka source service is located in a different VPC from RisingWave, use AWS PrivateLink to establish a secure and direct connection. For details on how to set up an AWS PrivateLink connection, see [Create an AWS PrivateLink connection](/sql/commands/sql-create-connection.md#create-an-aws-privatelink-connection).
 
-To create a Kafka source with a VPC connection, in the WITH section of your `CREATE SOURCE` or `CREATE TABLE` statement, specify the following parameters.
+To create a Kafka source with a PrivateLink connection, in the WITH section of your `CREATE SOURCE` or `CREATE TABLE` statement, specify the following parameters.
 
 |Parameter| Notes|
 |---|---|
 |`privatelink.targets`| The PrivateLink targets that correspond to the Kafka brokers. The targets should be in JSON format. Note that each target listed corresponds to each broker specified in the `properties.bootstrap.server` field. If the order is incorrect, there will be connectivity issues. |
-|`privatelink.endpoint`|The DNS name of the VPC endpoint. <br/> If you're using RisingWave Cloud, you can find the auto-generated endpoint after you created a connection. See details in [Create a VPC connection](/cloud/create-a-connection#whats-next).|
+|`privatelink.endpoint`|The DNS name of the VPC endpoint. <br/> If you're using RisingWave Cloud, you can find the auto-generated endpoint after you created a connection. See details in [Create a PrivateLink connection](/cloud/create-a-connection#whats-next).|
 |`connection.name`| The name of the connection. <br/> This parameter should only be included if you are using a connection created with the [`CREATE CONNECTION`](/sql/commands/sql-create-connection.md) statement. Omit this parameter if you have provisioned a VPC endpoint using `privatelink.endpoint` (recommended).|
 
 Here is an example of creating a Kafka source using a PrivateLink connection. Notice that `{"port": 9094}` corresponds to the broker `broker1-endpoint`, `{"port": 9095}` corresponds to the broker `broker2-endpoint`, and `{"port": 9096}` corresponds to the broker `broker3-endpoint`.