docs: fix console navigation to Connection tab and add Cloud Meta/PrivateLink navigation

Co-authored-by: cyberchen98 <44337247+cyberchen98@users.noreply.github.com>
Agent-Logs-Url: https://github.com/risingwavelabs/risingwave-docs/sessions/29ecca3e-90ff-438b-9837-562d8b835071

Author: 2 people

cloud/cloud-metadata.mdx

@@ -8,7 +8,11 @@ RisingWave Cloud exposes a set of environment-specific metadata values for each
 
 ## Where to find cloud metadata
 
-Navigate to your project in the [RisingWave Cloud Console](https://cloud.risingwave.com/project/home/), then select **Settings** → **Cloud metadata**.
+In the [RisingWave Cloud Console](https://cloud.risingwave.com), go to your project and click **Connection** in the left sidebar. Then select the **Cloud Meta** tab.
+
+<Frame>
+<img src="/images/cloud/cloud-metadata/connection-cloud-meta.png" alt="Cloud Meta tab in the Connection page of the RisingWave Cloud Console"/>
+</Frame>
 
 <Note>
 Cloud metadata is only available for projects on the **Standard** plan or above.

cloud/create-a-connection.mdx

@@ -30,8 +30,8 @@ You need to set up a PrivateLink service in your VPC and make sure it runs prope
 
 ## Create PrivateLink connection
 
-1. Go to the [**Project**](https://cloud.risingwave.com/project/home/) page and select the project you want to connect the VPC to.
-2. Select **PrivateLink** tab, and click **Create PrivateLink**.
+1. In the [RisingWave Cloud Console](https://cloud.risingwave.com), go to your project and click **Connection** in the left sidebar.
+2. Select the **PrivateLink** tab, and click **Create PrivateLink**.
 3. For **Name**, enter a descriptive name for the connection.
 4. For **Endpoint service name** or **Service attachment** or **Private link service resource ID:**
 
@@ -85,5 +85,5 @@ For details on how to use the VPC endpoint to create a source with the PrivateLi
 
 When you no longer need a connection:
 
-1. Go to the [**Connection**](https://cloud.risingwave.com/connection/) page and click **Create PrivateLink**.
+1. In the [RisingWave Cloud Console](https://cloud.risingwave.com), go to your project and click **Connection** in the left sidebar. Select the **PrivateLink** tab.
 2. Hover over the connection you want to drop and click the delete button, then confirm the deletion.

cloud/iam-role-assume.mdx

@@ -24,7 +24,7 @@ RisingWave Cloud (AWS account: <rw-account-id>)
 
 ## Required cloud metadata values
 
-Before you begin, retrieve the following values from your project's [Cloud metadata](/cloud/cloud-metadata) page in the RisingWave Cloud Console (**Settings** → **Cloud metadata**):
+Before you begin, retrieve the following values from your project's [Cloud metadata](/cloud/cloud-metadata) page in the RisingWave Cloud Console (**Connection** → **Cloud Meta** tab):
 
 | Metadata field | Where it's used |
 |:---------------|:----------------|

cloud/privatelink-overview.mdx

@@ -31,6 +31,10 @@ On the **RisingWave Cloud** side, RisingWave Cloud will create an endpoint (spec
 
 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.
 
+## Accessing PrivateLink in the Console
+
+In the [RisingWave Cloud Console](https://cloud.risingwave.com), go to your project and click **Connection** in the left sidebar. Then select the **PrivateLink** tab to create and manage PrivateLink connections.
+
 <Tip>
-When setting up an AWS endpoint service, add the **PrivateLink Principal** from your project's [Cloud metadata](/cloud/cloud-metadata) page to the service's allowed principals list so that RisingWave Cloud can connect.
+When setting up an AWS endpoint service, add the **PrivateLink Principal** from your project's **Cloud Meta** tab ([Cloud metadata](/cloud/cloud-metadata)) to the service's allowed principals list so that RisingWave Cloud can connect.
 </Tip>