@@ -32,7 +58,7 @@ For **Amazon S3**, you can use either **AWS Role ARN** or **AWS access key** for
To use an IAM Role for authentication, follow these steps:
-1. On the **Destination** page for Amazon S3, enter the **S3 URI**. Make sure that the S3 bucket is in the same AWS region as your TiDB cluster.
+1. On the **Destination** page for Amazon S3, enter the **S3 URI**. Make sure that the S3 bucket is in the same AWS region as your TiDB Cloud Dedicated clusterTiDB Cloud Premium instance.
2. Under **Bucket Access**, select **AWS Role ARN**.
3. To create a new Role ARN, click **Click here to create new one with AWS CloudFormation**. This template automatically configures the required permissions.
@@ -55,7 +81,7 @@ To use an IAM Role for authentication, follow these steps:
To use an access key for authentication, follow these steps:
-1. On the **Destination** page for Amazon S3, enter the **S3 URI**. Make sure that the S3 bucket is in the same AWS region as your TiDB cluster.
+1. On the **Destination** page for Amazon S3, enter the **S3 URI**. Make sure that the S3 bucket is in the same AWS region as your TiDB Cloud Dedicated clusterTiDB Cloud Premium instance.
2. Under **Bucket Access**, select **AWS Access Key**.
3. Fill in the following fields:
@@ -63,6 +89,9 @@ To use an access key for authentication, follow these steps:
- **Secret Access Key**
+
+
+
For **GCS**, before filling **GCS Endpoint**, you need to first grant the GCS bucket access. Take the following steps:
@@ -118,6 +147,11 @@ For **GCS**, before filling **GCS Endpoint**, you need to first grant the GCS bu
7. In the TiDB Cloud console, go to the Changefeed's **Destination** page, and fill in the **bucket gsutil URI** field.
+
+
+
+
+
For **Azure Blob Storage**, you must configure the container and get a SAS token in the Azure portal first. Take the following steps:
@@ -158,9 +192,62 @@ For **Azure Blob Storage**, you must configure the container and get a SAS token
- **SAS Token**: enter the generated SAS token obtained in step 3.
+
+
+
+
+
+
+
+For **Alibaba Cloud OSS**, follow these steps to configure the changefeed:
+
+1. In the [Alibaba Cloud console](https://www.alibabacloud.com/), perform the following prerequisite steps:
+
+ 1. Create an OSS bucket in the same region as your TiDB cluster. For detailed instructions, see [Create a bucket](https://www.alibabacloud.com/help/en/oss/user-guide/create-a-bucket-4).
+ 2. Create a RAM user for the changefeed and generate an AccessKey pair. For detailed instructions, see [Create an AccessKey pair](https://www.alibabacloud.com/help/en/ram/user-guide/create-an-accesskey-pair).
+ 3. Create and attach a custom RAM policy to the RAM user to grant only the minimum permissions required by the changefeed. For more information, see [Control access to OSS resources with RAM policies](https://www.alibabacloud.com/help/en/oss/user-guide/ram-policy).
+
+ - `oss:ListObjects`
+ - `oss:GetObject`
+ - `oss:PutObject`
+ - `oss:DeleteObject`
+
+ The following JSON example shows a policy with the required permissions. Replace `
` with the name of your OSS bucket.
+
+ ```json
+ {
+ "Version": "1",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "oss:ListObjects",
+ "oss:GetObject",
+ "oss:PutObject",
+ "oss:DeleteObject"
+ ],
+ "Resource": [
+ "acs:oss:*:*:",
+ "acs:oss:*:*:/*"
+ ]
+ }
+ ]
+ }
+ ```
+
+2. On the **Destination** page for Alibaba Cloud OSS, fill in the following fields:
+
+ - **Bucket URI**: enter the OSS URI in the format `oss:////`.
+ - **Access Key ID**: enter the AccessKey ID from the RAM user.
+ - **Access Key Secret**: enter the AccessKey Secret from the RAM user.
+
+