From 92ccb2b1df7ee3f48c431ae8d6e252a1dd53a601 Mon Sep 17 00:00:00 2001 From: Howard Chen Date: Mon, 5 Jan 2026 14:30:40 +0800 Subject: [PATCH 01/13] Add export backup guide for S3 and GCS. --- tidb-cloud/backup-and-restore.md | 55 ++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index 632b20508627e..f903f7881aeca 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -176,6 +176,61 @@ To apply a manual backup to your TiDB Cloud Dedicated cluster, perform the follo 4. Click **Confirm**. Then your cluster data is backed up. +### Export backups + +To export a specific backup to Cloud Storage, perform the following steps: + + + +
+1. Navigate to the [**Backup**](#view-the-backup-page) page of your cluster. + +2. Locate the backup you want to export, and click **...** > **Export** in the **Action** column. + +3. In the **Export Backup to AWS S3** dialog, enter the **Folder URI** and select a region for the backup bucket. + +4. Click **Generate Command** to see the command for configuring permissions. + + - **With AWS CLI**: + Execute the generated command on AWS to grant TiDB Cloud access to your AWS sources. + + - **With AWS Console**: + 1. Navigate to the Amazon S3 console. + 2. Go to the bucket detail page and switch to the **Permissions** tab. + 3. Scroll down to **Bucket Policy**, and click **Edit**. + 4. Copy the policy content from the generated command and paste it into the policy editor. + 5. Click **Save Changes**. + +5. Click **Export** to start the export process. +
+ +
+To export a specific backup to Google Cloud Storage (GCS), perform the following steps: + +1. Navigate to the [**Backup**](#view-the-backup-page) page of your cluster. + +2. Locate the backup you want to export, and click **...** > **Export** in the **Action** column. + +3. In the **Export Backup to Google Cloud Storage** dialog, note the **Google Cloud Service Account ID** we will use later. + +4. In Google Cloud Console, ensure a role exists with the following permissions: + + - `storage.buckets.get` + - `storage.objects.list` + - `storage.objects.create` + - `storage.objects.delete` + +5. In **Cloud Storage** > **Buckets**, select the target bucket, and go to **Permissions** > **Grant Access**. + +6. In **New principals**, enter the **Service Account ID** noted in step 3, select the role from step 4, and click **Save**. + +7. Switch to the **Configuration** tab, copy the **gsutil URI**, and paste it into the **Export Path** field in the **Export Backup to Google Cloud Storage** dialog. You can append a path suffix to the URI to create a subdirectory. + +8. Click **Export** to start the export process. +
+ + + ### Delete backups #### Delete backup files From 684f9df3d010781e2ea16ec32f883009b57add78 Mon Sep 17 00:00:00 2001 From: Ginkgoch Date: Mon, 5 Jan 2026 14:34:02 +0800 Subject: [PATCH 02/13] Update tidb-cloud/backup-and-restore.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-cloud/backup-and-restore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index f903f7881aeca..88711e01b94de 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -192,7 +192,7 @@ To export a specific backup to Cloud Storage, perform the following steps: 4. Click **Generate Command** to see the command for configuring permissions. - **With AWS CLI**: - Execute the generated command on AWS to grant TiDB Cloud access to your AWS sources. + Execute the generated command on AWS to grant TiDB Cloud access to your AWS S3 bucket. - **With AWS Console**: 1. Navigate to the Amazon S3 console. From ecd11777f1da6b3922c82d2109fc29d81d34c20b Mon Sep 17 00:00:00 2001 From: Ginkgoch Date: Mon, 5 Jan 2026 14:34:19 +0800 Subject: [PATCH 03/13] Update tidb-cloud/backup-and-restore.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-cloud/backup-and-restore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index 88711e01b94de..981691a1d3b6d 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -211,7 +211,7 @@ To export a specific backup to Google Cloud Storage (GCS), perform the following 2. Locate the backup you want to export, and click **...** > **Export** in the **Action** column. -3. In the **Export Backup to Google Cloud Storage** dialog, note the **Google Cloud Service Account ID** we will use later. +3. In the **Export Backup to Google Cloud Storage** dialog, note the **Google Cloud Service Account ID**, which is required for a later step. 4. In Google Cloud Console, ensure a role exists with the following permissions: From d475afcc79a543836cb9f7105d380b2223bcd0cd Mon Sep 17 00:00:00 2001 From: Ginkgoch Date: Mon, 5 Jan 2026 14:34:41 +0800 Subject: [PATCH 04/13] Update tidb-cloud/backup-and-restore.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-cloud/backup-and-restore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index 981691a1d3b6d..4c1830fd292a3 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -213,7 +213,7 @@ To export a specific backup to Google Cloud Storage (GCS), perform the following 3. In the **Export Backup to Google Cloud Storage** dialog, note the **Google Cloud Service Account ID**, which is required for a later step. -4. In Google Cloud Console, ensure a role exists with the following permissions: +4. In Google Cloud Console, create a custom IAM role or make sure that an existing role has the following permissions: - `storage.buckets.get` - `storage.objects.list` From 11c5a993d2913ab9317babdd09ea5ebd7928b38b Mon Sep 17 00:00:00 2001 From: Howard Chen Date: Mon, 5 Jan 2026 14:36:34 +0800 Subject: [PATCH 05/13] Remove GCS abbr. --- tidb-cloud/backup-and-restore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index 4c1830fd292a3..a99bd8e988c2e 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -205,7 +205,7 @@ To export a specific backup to Cloud Storage, perform the following steps:
-To export a specific backup to Google Cloud Storage (GCS), perform the following steps: +To export a specific backup to Google Cloud Storage, perform the following steps: 1. Navigate to the [**Backup**](#view-the-backup-page) page of your cluster. From c6a8c5bf985bb26c55d4f631e05f330b2b003e38 Mon Sep 17 00:00:00 2001 From: Howard Chen Date: Mon, 5 Jan 2026 14:38:40 +0800 Subject: [PATCH 06/13] Improve a casing. --- tidb-cloud/backup-and-restore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index a99bd8e988c2e..8cc5512b2d46c 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -213,7 +213,7 @@ To export a specific backup to Google Cloud Storage, perform the following steps 3. In the **Export Backup to Google Cloud Storage** dialog, note the **Google Cloud Service Account ID**, which is required for a later step. -4. In Google Cloud Console, create a custom IAM role or make sure that an existing role has the following permissions: +4. In Google Cloud console, create a custom IAM role or make sure that an existing role has the following permissions: - `storage.buckets.get` - `storage.objects.list` From b89be80ed1d466084250faa5d023ecce3324b628 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Wed, 7 Jan 2026 19:42:35 +0800 Subject: [PATCH 07/13] refine wording --- tidb-cloud/backup-and-restore.md | 36 +++++++++++++++++++------------- 1 file changed, 22 insertions(+), 14 deletions(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index 8cc5512b2d46c..8fac8a8be5eba 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -178,55 +178,63 @@ To apply a manual backup to your TiDB Cloud Dedicated cluster, perform the follo ### Export backups -To export a specific backup to Cloud Storage, perform the following steps: +
+ +To export a specific backup to cloud storage, such as and Google Cloud Storage, perform the following steps: -
+
+ 1. Navigate to the [**Backup**](#view-the-backup-page) page of your cluster. 2. Locate the backup you want to export, and click **...** > **Export** in the **Action** column. -3. In the **Export Backup to AWS S3** dialog, enter the **Folder URI** and select a region for the backup bucket. +3. In the **Export Backup to AWS S3** dialog, enter the **Folder URI**, and then select a region for the backup bucket. 4. Click **Generate Command** to see the command for configuring permissions. - **With AWS CLI**: - Execute the generated command on AWS to grant TiDB Cloud access to your AWS S3 bucket. + + Execute the generated command on AWS to grant TiDB Cloud access to your Amazon S3 bucket. - **With AWS Console**: - 1. Navigate to the Amazon S3 console. - 2. Go to the bucket detail page and switch to the **Permissions** tab. - 3. Scroll down to **Bucket Policy**, and click **Edit**. - 4. Copy the policy content from the generated command and paste it into the policy editor. + + 1. Navigate to the [Amazon S3 console](https://console.aws.amazon.com/s3/). + 2. Go to the bucket detail page, and then switch to the **Permissions** tab. + 3. Scroll down to **Bucket Policy**, and then click **Edit**. + 4. Copy the policy content from the generated command, and then paste it into the policy editor. 5. Click **Save Changes**. 5. Click **Export** to start the export process. +
+ To export a specific backup to Google Cloud Storage, perform the following steps: 1. Navigate to the [**Backup**](#view-the-backup-page) page of your cluster. -2. Locate the backup you want to export, and click **...** > **Export** in the **Action** column. +2. Locate the backup you want to export, and then click **...** > **Export** in the **Action** column. -3. In the **Export Backup to Google Cloud Storage** dialog, note the **Google Cloud Service Account ID**, which is required for a later step. +3. In the **Export Backup to Google Cloud Storage** dialog, note down the **Google Cloud Service Account ID**, which is required for a later step. -4. In Google Cloud console, create a custom IAM role or make sure that an existing role has the following permissions: +4. In the [Google Cloud console](https://console.cloud.google.com/), create a custom IAM role, or make sure that an existing role has the following permissions: - `storage.buckets.get` - `storage.objects.list` - `storage.objects.create` - `storage.objects.delete` -5. In **Cloud Storage** > **Buckets**, select the target bucket, and go to **Permissions** > **Grant Access**. +5. In **Cloud Storage** > **Buckets**, select the target bucket, and then go to **Permissions** > **Grant Access**. -6. In **New principals**, enter the **Service Account ID** noted in step 3, select the role from step 4, and click **Save**. +6. In **New principals**, enter the **Service Account ID** that you noted down in Step 3, select the role from Step 4, and then click **Save**. -7. Switch to the **Configuration** tab, copy the **gsutil URI**, and paste it into the **Export Path** field in the **Export Backup to Google Cloud Storage** dialog. You can append a path suffix to the URI to create a subdirectory. +7. Switch to the **Configuration** tab, copy the **gsutil URI**, and then paste it into the **Export Path** field in the **Export Backup to Google Cloud Storage** dialog. You can append a path suffix to the URI to create a subdirectory. 8. Click **Export** to start the export process. +
From 82550a0d27fab3fb4f39210ecc095d4428da39ff Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Thu, 8 Jan 2026 14:39:21 +0800 Subject: [PATCH 08/13] Update tidb-cloud/backup-and-restore.md --- tidb-cloud/backup-and-restore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index 8fac8a8be5eba..aeca0a64f77a3 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -190,7 +190,7 @@ To export a specific backup to cloud storage, such as and Google Cloud Storage, 2. Locate the backup you want to export, and click **...** > **Export** in the **Action** column. -3. In the **Export Backup to AWS S3** dialog, enter the **Folder URI**, and then select a region for the backup bucket. +3. In the **Export Backup to Amazon S3** dialog, enter the **Folder URI**, and then select a bucket region for the backup bucket. 4. Click **Generate Command** to see the command for configuring permissions. From e01167b7fd09e4a62b61242876613e3887e54d5b Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Mon, 12 Jan 2026 09:24:55 +0800 Subject: [PATCH 09/13] Apply suggestions from code review Co-authored-by: Aolin --- tidb-cloud/backup-and-restore.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index aeca0a64f77a3..e713cb82a3fea 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -178,21 +178,21 @@ To apply a manual backup to your TiDB Cloud Dedicated cluster, perform the follo ### Export backups -
- -To export a specific backup to cloud storage, such as and Google Cloud Storage, perform the following steps: +To export a specific backup to cloud storage, such as Amazon S3 or Google Cloud Storage, follow the steps for your target storage provider.
+To export a backup to Amazon S3, perform the following steps: + 1. Navigate to the [**Backup**](#view-the-backup-page) page of your cluster. -2. Locate the backup you want to export, and click **...** > **Export** in the **Action** column. +2. Locate the backup you want to export, and then click **...** > **Export** in the **Action** column. -3. In the **Export Backup to Amazon S3** dialog, enter the **Folder URI**, and then select a bucket region for the backup bucket. +3. In the **Export Backup to Amazon S3** dialog, enter the **Folder URI** field, and then select a bucket region for the backup bucket. -4. Click **Generate Command** to see the command for configuring permissions. +4. Click **Generate Command** to view the command for configuring permissions. - **With AWS CLI**: @@ -201,10 +201,10 @@ To export a specific backup to cloud storage, such as and Google Cloud Storage, - **With AWS Console**: 1. Navigate to the [Amazon S3 console](https://console.aws.amazon.com/s3/). - 2. Go to the bucket detail page, and then switch to the **Permissions** tab. - 3. Scroll down to **Bucket Policy**, and then click **Edit**. + 2. Open the target bucket details page, and then click the **Permissions** tab. + 3. Scroll to **Bucket policy**, and then click **Edit**. 4. Copy the policy content from the generated command, and then paste it into the policy editor. - 5. Click **Save Changes**. + 5. Click **Save changes**. 5. Click **Export** to start the export process. @@ -212,7 +212,7 @@ To export a specific backup to cloud storage, such as and Google Cloud Storage,
-To export a specific backup to Google Cloud Storage, perform the following steps: +To export a backup to Google Cloud Storage, perform the following steps: 1. Navigate to the [**Backup**](#view-the-backup-page) page of your cluster. @@ -220,18 +220,18 @@ To export a specific backup to Google Cloud Storage, perform the following steps 3. In the **Export Backup to Google Cloud Storage** dialog, note down the **Google Cloud Service Account ID**, which is required for a later step. -4. In the [Google Cloud console](https://console.cloud.google.com/), create a custom IAM role, or make sure that an existing role has the following permissions: +4. In the [Google Cloud console](https://console.cloud.google.com/), create a custom IAM role with the following permissions. If you use an existing role, verify that it has these permissions. - `storage.buckets.get` - `storage.objects.list` - `storage.objects.create` - `storage.objects.delete` -5. In **Cloud Storage** > **Buckets**, select the target bucket, and then go to **Permissions** > **Grant Access**. +5. Go to **Cloud Storage** > **Buckets**, select the target bucket, and then click **Permissions** > **Grant Access**. -6. In **New principals**, enter the **Service Account ID** that you noted down in Step 3, select the role from Step 4, and then click **Save**. +6. In **New principals**, enter the **Service Account ID** from step 3, assign the role from step 4, and then click **Save**. -7. Switch to the **Configuration** tab, copy the **gsutil URI**, and then paste it into the **Export Path** field in the **Export Backup to Google Cloud Storage** dialog. You can append a path suffix to the URI to create a subdirectory. +7. Open the **Configuration** tab, copy the **gsutil URI**, and paste it into the **Export Path** field in the **Export Backup to Google Cloud Storage** dialog. To export to a subdirectory, append a path suffix to the URI. 8. Click **Export** to start the export process. From 4a123c722447335c03cf7bc5098e06810a2a1d71 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Wed, 4 Feb 2026 17:55:24 +0800 Subject: [PATCH 10/13] Standardize support request text; add export note Standardize wording across TiDB Cloud docs for requesting private-preview features by directing users to the "Support Tickets" Help Center (https://tidb.support.pingcap.com/servicedesk/customer/portals) and providing consistent ticket instructions. Also add a new note in backup-and-restore.md explaining that export backups to cloud storage is available upon request and how to submit a ticket. Small copy and punctuation adjustments made in multiple tidb-cloud docs for consistency. --- tidb-cloud/backup-and-restore.md | 4 ++++ tidb-cloud/changefeed-sink-to-apache-kafka.md | 2 +- tidb-cloud/changefeed-sink-to-mysql.md | 2 +- tidb-cloud/configure-sql-users.md | 2 +- tidb-cloud/essential-database-audit-logging.md | 2 +- tidb-cloud/features.md | 2 +- tidb-cloud/premium/create-tidb-instance-premium.md | 4 ++-- tidb-cloud/size-your-cluster.md | 4 ++-- tidb-cloud/tidb-cloud-auditing.md | 4 ++-- tidb-cloud/tidb-cloud-release-notes.md | 2 +- tidb-cloud/tidb-cloud-support.md | 4 ++-- 11 files changed, 18 insertions(+), 14 deletions(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index e713cb82a3fea..7d2620f538b25 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -180,6 +180,10 @@ To apply a manual backup to your TiDB Cloud Dedicated cluster, perform the follo To export a specific backup to cloud storage, such as Amazon S3 or Google Cloud Storage, follow the steps for your target storage provider. +> **Note:** +> +> Currently, this feature is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for the export backups feature" in the **Description** field, and then click **Submit**. +
diff --git a/tidb-cloud/changefeed-sink-to-apache-kafka.md b/tidb-cloud/changefeed-sink-to-apache-kafka.md index a5fdb5a283f14..6f98566d5cc8b 100644 --- a/tidb-cloud/changefeed-sink-to-apache-kafka.md +++ b/tidb-cloud/changefeed-sink-to-apache-kafka.md @@ -131,7 +131,7 @@ It is **NOT** recommended to use Public IP in a production environment.
-Currently, the VPC Peering feature for {{{ .premium }}} instances is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply for VPC Peering for {{{ .premium }}} instance" in the **Description** field and click **Submit**. +Currently, the VPC Peering feature for {{{ .premium }}} instances is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the Help Center. Create a ticket, fill in "Apply for VPC Peering for {{{ .premium }}} instance" in the **Description** field, and then click **Submit**.
diff --git a/tidb-cloud/changefeed-sink-to-mysql.md b/tidb-cloud/changefeed-sink-to-mysql.md index 676bf3d62dafa..d03e6059cc3fc 100644 --- a/tidb-cloud/changefeed-sink-to-mysql.md +++ b/tidb-cloud/changefeed-sink-to-mysql.md @@ -86,7 +86,7 @@ Make sure that your TiDB Cloud instance can connect to the MySQL service. > **Note:** > -> Currently, the VPC Peering feature for {{{ .premium }}} instances is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply for VPC Peering for {{{ .premium }}} instance" in the **Description** field and click **Submit**. +> Currently, this feature is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for VPC Peering for {{{ .premium }}} instance" in the **Description** field, and then click **Submit**. Private endpoints leverage **Private Link** or **Private Service Connect** technologies from cloud providers, enabling resources in your VPC to connect to services in other VPCs through private IP addresses, as if those services were hosted directly within your VPC. diff --git a/tidb-cloud/configure-sql-users.md b/tidb-cloud/configure-sql-users.md index 935a7bdb53d5c..db6352b2396bd 100644 --- a/tidb-cloud/configure-sql-users.md +++ b/tidb-cloud/configure-sql-users.md @@ -9,7 +9,7 @@ This document describes how to manage database users and roles using the **SQL U > **Note:** > -> - The **SQL Users** page is in beta and is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply for the SQL Users page" in the **Description** field and click **Submit**. +> - The **SQL Users** page is in beta and is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for the SQL Users page" in the **Description** field, and then click **Submit**. > - Database users and roles are independent of [organization and project users and roles](/tidb-cloud/manage-user-access.md). Database users are used to access databases in a TiDB cluster, while organization and project users are used to access organizations and projects in the [TiDB Cloud console](https://tidbcloud.com/). > - In addition to the **SQL Users** page, you can also manage database users and roles by connecting to your cluster with a SQL client and writing SQL statements. For more information, see [TiDB User Account Management](https://docs.pingcap.com/tidb/dev/user-account-management). diff --git a/tidb-cloud/essential-database-audit-logging.md b/tidb-cloud/essential-database-audit-logging.md index 88be732f5063e..3a58d2b5c3dbc 100644 --- a/tidb-cloud/essential-database-audit-logging.md +++ b/tidb-cloud/essential-database-audit-logging.md @@ -10,7 +10,7 @@ aliases: ['/tidbcloud/serverless-audit-logging'] > **Note:** > -> Currently, the database audit logging feature is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply for {{{ .essential }}} database audit logging" in the **Description** field and click **Submit**. +> Currently, the database audit logging feature is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for {{{ .essential }}} database audit logging" in the **Description** field, and then click **Submit**. To evaluate the effectiveness of user access policies and other information security measures of your organization, it is a security best practice to periodically analyze database audit logs. diff --git a/tidb-cloud/features.md b/tidb-cloud/features.md index 5d437ec70add0..a30b05a978ce9 100644 --- a/tidb-cloud/features.md +++ b/tidb-cloud/features.md @@ -279,4 +279,4 @@ This document lists the feature support status for different TiDB Cloud plans, i > **Tip:** > -> To request a feature in private preview, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in the feature name in the **Description** field and click **Submit**. \ No newline at end of file +> To request a feature in private preview, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for " in the **Description** field, and then click **Submit**. \ No newline at end of file diff --git a/tidb-cloud/premium/create-tidb-instance-premium.md b/tidb-cloud/premium/create-tidb-instance-premium.md index 5ffdd6823be2c..7efed443f5283 100644 --- a/tidb-cloud/premium/create-tidb-instance-premium.md +++ b/tidb-cloud/premium/create-tidb-instance-premium.md @@ -9,7 +9,7 @@ This document describes how to create a {{{ .premium }}} instance in the [TiDB C > **Note:** > -> - Currently, {{{ .premium }}} is only available upon request. To request it, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply for {{{ .premium }}}" in the **Description** field and click **Submit**. +> - Currently, {{{ .premium }}} is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for {{{ .premium }}}" in the **Description** in the **Description** field, and then click **Submit**. > - To learn how to create a TiDB Cloud Dedicated cluster, see [Create a TiDB Cloud Dedicated Cluster](/tidb-cloud/create-tidb-cluster.md). ## Before you begin @@ -43,7 +43,7 @@ If you have the `Organization Owner` role, you can create a {{{ .premium }}} ins > **Note:** > - > If **Switch to Private Preview** is not visible in the lower-left corner of your TiDB Cloud console, it means that your organization has not been invited to the private preview of {{{ .premium }}}. In this case, you can click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support** to apply for {{{ .premium }}}. + > If **Switch to Private Preview** is not visible in the lower-left corner of your TiDB Cloud console, it means that your organization has not been invited to the private preview of {{{ .premium }}}. In this case, you can click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for the private preview of {{{ .premium }}}" in the **Description** field, and then click **Submit**. 2. On the **TiDB Instances** page, click **Create Instance**. 3. Enter a name for your {{{ .premium }}} instance. diff --git a/tidb-cloud/size-your-cluster.md b/tidb-cloud/size-your-cluster.md index 1a1a3d50381f8..7584ae528aeb6 100644 --- a/tidb-cloud/size-your-cluster.md +++ b/tidb-cloud/size-your-cluster.md @@ -211,7 +211,7 @@ The Standard storage type is applied automatically to new clusters hosted on AWS #### Performance and Plus storage -The Performance and Plus storage provide higher performance and stability, with pricing that reflects these enhanced capabilities. Currently, these two storage types are only available upon request for clusters deployed on AWS. To request the Performance or Plus storage, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply for TiKV storage type" in the **Description** field and click **Submit**. +The Performance and Plus storage provide higher performance and stability, with pricing that reflects these enhanced capabilities. Currently, these two storage types are only available upon request for clusters deployed on AWS. To request the Performance or Plus storage, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for TiKV storage type" in the **Description** field, and then click **Submit**. ## Size TiFlash @@ -269,4 +269,4 @@ The Basic storage is ideal for most workloads, providing a balance between perfo #### Plus storage -The Plus storage provides higher performance and stability, with pricing that reflects these enhanced capabilities. Currently, this storage type is only available upon request for clusters deployed on AWS. To request it, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply for TiFlash storage type" in the **Description** field and click **Submit**. \ No newline at end of file +The Plus storage provides higher performance and stability, with pricing that reflects these enhanced capabilities. Currently, this storage type is only available upon request for clusters deployed on AWS. To request it, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for TiFlash storage type" in the **Description** field, and then click **Submit**. \ No newline at end of file diff --git a/tidb-cloud/tidb-cloud-auditing.md b/tidb-cloud/tidb-cloud-auditing.md index e6d69f2bd5982..48d57f029083a 100644 --- a/tidb-cloud/tidb-cloud-auditing.md +++ b/tidb-cloud/tidb-cloud-auditing.md @@ -9,7 +9,7 @@ TiDB Cloud provides an audit logging feature that records user access activities > **Note:** > -> Currently, the database audit logging feature is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply for database audit logging" in the **Description** field and click **Submit**. +> Currently, the database audit logging feature is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for database audit logging" in the **Description** field, and then click **Submit**. To evaluate the effectiveness of user access policies and other information security measures of your organization, it is a security best practice to periodically analyze database audit logs. @@ -36,7 +36,7 @@ TiDB Cloud supports recording the audit logs of a TiDB Cloud Dedicated cluster t > **Note:** > -> For TiDB clusters deployed on AWS, you can choose to store audit log files in TiDB Cloud when enabling database audit logging. Currently, this feature is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply to store audit log files in TiDB Cloud" in the **Description** field and click **Submit**. +> For TiDB clusters deployed on AWS, you can choose to store audit log files in TiDB Cloud when enabling database audit logging. Currently, this feature is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply to store audit log files in TiDB Cloud" in the **Description** field, and then click **Submit**. ### Enable audit logging for AWS diff --git a/tidb-cloud/tidb-cloud-release-notes.md b/tidb-cloud/tidb-cloud-release-notes.md index e1470feb56f0d..a3168f58e8140 100644 --- a/tidb-cloud/tidb-cloud-release-notes.md +++ b/tidb-cloud/tidb-cloud-release-notes.md @@ -533,7 +533,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c - [TiDB Cloud Serverless](/tidb-cloud/select-cluster-tier.md#starter) database audit logging (beta) is now available upon request. This feature lets you record a history of user access details (such as any SQL statements executed) in logs. - To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com) and click **Request Support**. Then, fill in "Apply for TiDB Cloud Serverless database audit logging" in the Description field and click **Submit**. + To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for TiDB Cloud Serverless database audit logging" in the **Description** field, and then click **Submit**. - [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) supports user-controlled log redaction. diff --git a/tidb-cloud/tidb-cloud-support.md b/tidb-cloud/tidb-cloud-support.md index cfac2666c559f..8e500aed60650 100644 --- a/tidb-cloud/tidb-cloud-support.md +++ b/tidb-cloud/tidb-cloud-support.md @@ -17,8 +17,8 @@ The [PingCAP Help Center](https://tidb.support.pingcap.com/servicedesk/customer/ You can access the PingCAP Help Center via directly, or through the [TiDB Cloud console](https://tidbcloud.com/) in the following ways: -- Click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/), and then click **Request Support**. -- Click **Support** in the lower-left corner of [TiDB Cloud console](https://tidbcloud.com/), and then click **Create Ticket**. +- Click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/), and then click **Support Tickets**. +- Click **Support** in the lower-left corner of [TiDB Cloud console](https://tidbcloud.com/), and then in the **Talk to an expert** area click **PingCAP Help Center**. - On the [**Clusters**](https://tidbcloud.com/project/clusters) page of your project, click **...** in the row of your cluster, and then select **Get Support**. - On your cluster overview page, click **...** in the upper-right corner, and then select **Get Support**. From 860e594deb673c887caf8f2b8aab79f19a15b8b4 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 4 Feb 2026 20:15:45 +0800 Subject: [PATCH 11/13] Apply suggestions from code review Co-authored-by: Grace Cai --- tidb-cloud/changefeed-sink-to-apache-kafka.md | 2 +- tidb-cloud/premium/create-tidb-instance-premium.md | 2 +- tidb-cloud/tidb-cloud-support.md | 4 +++- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/changefeed-sink-to-apache-kafka.md b/tidb-cloud/changefeed-sink-to-apache-kafka.md index 6f98566d5cc8b..406c8feeaf6fe 100644 --- a/tidb-cloud/changefeed-sink-to-apache-kafka.md +++ b/tidb-cloud/changefeed-sink-to-apache-kafka.md @@ -131,7 +131,7 @@ It is **NOT** recommended to use Public IP in a production environment.
-Currently, the VPC Peering feature for {{{ .premium }}} instances is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the Help Center. Create a ticket, fill in "Apply for VPC Peering for {{{ .premium }}} instance" in the **Description** field, and then click **Submit**. +Currently, the VPC Peering feature for {{{ .premium }}} instances is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for VPC Peering for {{{ .premium }}} instance" in the **Description** field, and then click **Submit**.
diff --git a/tidb-cloud/premium/create-tidb-instance-premium.md b/tidb-cloud/premium/create-tidb-instance-premium.md index 7efed443f5283..4bc1c2abd0422 100644 --- a/tidb-cloud/premium/create-tidb-instance-premium.md +++ b/tidb-cloud/premium/create-tidb-instance-premium.md @@ -9,7 +9,7 @@ This document describes how to create a {{{ .premium }}} instance in the [TiDB C > **Note:** > -> - Currently, {{{ .premium }}} is only available upon request. To request this feature, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for {{{ .premium }}}" in the **Description** in the **Description** field, and then click **Submit**. +> - Currently, {{{ .premium }}} is only available upon request. To request {{{ .premium }}}, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for {{{ .premium }}}" in the **Description** in the **Description** field, and then click **Submit**. > - To learn how to create a TiDB Cloud Dedicated cluster, see [Create a TiDB Cloud Dedicated Cluster](/tidb-cloud/create-tidb-cluster.md). ## Before you begin diff --git a/tidb-cloud/tidb-cloud-support.md b/tidb-cloud/tidb-cloud-support.md index 8e500aed60650..c99391f492643 100644 --- a/tidb-cloud/tidb-cloud-support.md +++ b/tidb-cloud/tidb-cloud-support.md @@ -18,7 +18,9 @@ The [PingCAP Help Center](https://tidb.support.pingcap.com/servicedesk/customer/ You can access the PingCAP Help Center via directly, or through the [TiDB Cloud console](https://tidbcloud.com/) in the following ways: - Click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/), and then click **Support Tickets**. -- Click **Support** in the lower-left corner of [TiDB Cloud console](https://tidbcloud.com/), and then in the **Talk to an expert** area click **PingCAP Help Center**. +- Click **Support** in the lower-left corner of [TiDB Cloud console](https://tidbcloud.com/), and then do one of the following depending on your support plan: + - **Basic**: in the **Account & Billing** area, click **Account/Billing issues**. + - **Developer**, **Enterprise**, or **Premium**: in the **Talk to an expert** area, click **PingCAP Help Center**. - On the [**Clusters**](https://tidbcloud.com/project/clusters) page of your project, click **...** in the row of your cluster, and then select **Get Support**. - On your cluster overview page, click **...** in the upper-right corner, and then select **Get Support**. From b1cdff79c32cccf1d3fd973d150e8543e046978f Mon Sep 17 00:00:00 2001 From: houfaxin Date: Wed, 4 Feb 2026 20:31:07 +0800 Subject: [PATCH 12/13] Update features.md --- tidb-cloud/features.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/features.md b/tidb-cloud/features.md index 833ea0e037e12..a9bccd0528606 100644 --- a/tidb-cloud/features.md +++ b/tidb-cloud/features.md @@ -333,4 +333,4 @@ This document lists the feature support status for different TiDB Cloud plans, i > **Tip:** > -> To request a feature in private preview, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for " in the **Description** field, and then click **Submit**. \ No newline at end of file +> To request a feature in private preview, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for " in the **Description** field, and then click **Submit**. \ No newline at end of file From 730f27b5479c0dd46c84d5cef7ba21f11af95ee8 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 4 Feb 2026 20:42:19 +0800 Subject: [PATCH 13/13] Apply suggestion from @hfxsd --- tidb-cloud/features.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/features.md b/tidb-cloud/features.md index a9bccd0528606..6f252433bbdcb 100644 --- a/tidb-cloud/features.md +++ b/tidb-cloud/features.md @@ -333,4 +333,4 @@ This document lists the feature support status for different TiDB Cloud plans, i > **Tip:** > -> To request a feature in private preview, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for " in the **Description** field, and then click **Submit**. \ No newline at end of file +> To request a feature in private preview, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com), and then click **Support Tickets** to go to the [Help Center](https://tidb.support.pingcap.com/servicedesk/customer/portals). Create a ticket, fill in "Apply for ``" in the **Description** field, and then click **Submit**. \ No newline at end of file