Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Grace Cai <qqzczy@126.com>
  • Loading branch information
shiyuhang0 and qiancai authored Jan 2, 2025
1 parent 26250fb commit 1a74cee
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 6 deletions.
4 changes: 2 additions & 2 deletions tidb-cloud/serverless-export.md
Original file line number Diff line number Diff line change
Expand Up @@ -271,7 +271,7 @@ ticloud serverless export create -c <cluster-id> --target-type S3 --s3.uri <uri>
- **Data Format**: choose **SQL**, **CSV**, or **Parquet**.
- **Compression**: choose **Gzip**, **Snappy**, **Zstd**, or **None**.
- **Folder URI**: enter the URI of the Google Cloud Storage with the `gs://<bucket-name>/<folder-path>/` format.
- **Bucket Access**: upload the Google Cloud credentials file which has permission to access the bucket.
- **Bucket Access**: upload the Google Cloud credentials file that has permission to access the bucket.

4. Click **Export**.

Expand Down Expand Up @@ -302,7 +302,7 @@ ticloud serverless export create -c <cluster-id> --target-type GCS --gcs.uri <ur

2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane.

3. On the **Import** page, click **Export Data to** in the upper-right corner, then choose **Azure Blob Storage** from the drop-down list. Fill in the following parameters:
3. On the **Import** page, click **Export Data to** in the upper-right corner, and then choose **Azure Blob Storage** from the drop-down list. Fill in the following parameters:

- **Task Name**: enter a name for the export task. The default value is `SNAPSHOT_{snapshot_time}`.
- **Exported Data**: choose the databases and tables you want to export.
Expand Down
10 changes: 6 additions & 4 deletions tidb-cloud/serverless-external-storage.md
Original file line number Diff line number Diff line change
Expand Up @@ -199,13 +199,15 @@ Take the following steps to configure a service account key:

![service-account-key](/media/tidb-cloud/serverless-external-storage/gcs-service-account-key.png)

3. Choose the default `JSON` key type, and then click the **CREATE** button to download the Google Cloud credentials file. The file contains the service account key that you need to configure the GCS access for the TiDB Cloud Serverless cluster.
3. Choose the default `JSON` key type, and then click **CREATE** to download the Google Cloud credentials file. The file contains the service account key that you need to use when configuring the GCS access for the TiDB Cloud Serverless cluster.

## Configure Azure Blob Storage access

To allow TiDB Serverless to access your Azure Blob container, you need to configure the Azure Blob access for the container. You can use a service SAS token to configure the container access.
To allow TiDB Serverless to access your Azure Blob container, you need to create a service SAS token for the container.

It is recommended that you use [Azure ARM template](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/overview) to create a SAS token. Take the following steps to create one:
You can create a SAS token either using an [Azure ARM template](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/overview) (recommended) or manual configuration.

To create a SAS token using an Azure ARM template, take the following steps:

1. Open the **Import** page for your target cluster.

Expand All @@ -217,7 +219,7 @@ It is recommended that you use [Azure ARM template](https://learn.microsoft.com/

1. Click **Export data to...** > **Azure Blob Storage**. If your cluster has neither imported nor exported any data before, click **Click here to export data to...** > **Azure Blob Storage** at the bottom of the page.

2. Click **Click here to create a new one with Azure ARM template** under the SAS Token field.
2. Scroll down to the **Azure Blob Storage Settings** area, and then click **Click here to create a new one with Azure ARM template** under the SAS Token field.

3. Create a SAS token with the Azure ARM template.

Expand Down

0 comments on commit 1a74cee

Please sign in to comment.