diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index 632b20508627e..7d2620f538b25 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -176,6 +176,73 @@ 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, 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**. + + + +
+ +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 then click **...** > **Export** in the **Action** column. + +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 view the command for configuring permissions. + + - **With AWS CLI**: + + 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](https://console.aws.amazon.com/s3/). + 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 **Export** to start the export process. + +
+ +
+ +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. + +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 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 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. Go to **Cloud Storage** > **Buckets**, select the target bucket, and then click **Permissions** > **Grant Access**. + +6. In **New principals**, enter the **Service Account ID** from step 3, assign the role from step 4, and then click **Save**. + +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. + +
+ + + ### Delete backups #### Delete backup files diff --git a/tidb-cloud/changefeed-sink-to-apache-kafka.md b/tidb-cloud/changefeed-sink-to-apache-kafka.md index ff506f5bb6c86..b1d8b0b6a48a2 100644 --- a/tidb-cloud/changefeed-sink-to-apache-kafka.md +++ b/tidb-cloud/changefeed-sink-to-apache-kafka.md @@ -123,7 +123,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](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/changefeed-sink-to-mysql.md b/tidb-cloud/changefeed-sink-to-mysql.md index 297333547c74a..587c6c87bb48b 100644 --- a/tidb-cloud/changefeed-sink-to-mysql.md +++ b/tidb-cloud/changefeed-sink-to-mysql.md @@ -78,7 +78,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 4b243dca451a5..6b511807b58bb 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 ab1634898f318..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 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 6b7fc49119ded..4e555836ff4ae 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 {{{ .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 @@ -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 a6cf728b082da..b9013027b432b 100644 --- a/tidb-cloud/tidb-cloud-release-notes.md +++ b/tidb-cloud/tidb-cloud-release-notes.md @@ -85,4 +85,4 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c - **TiDB Cloud Dedicated** - - Upgrade the default TiDB version of new [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters from [v8.5.4](https://docs.pingcap.com/tidb/v8.5/release-8.5.4/) to [v8.5.5](https://docs.pingcap.com/tidb/v8.5/release-8.5.5/). \ No newline at end of file + - Upgrade the default TiDB version of new [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters from [v8.5.4](https://docs.pingcap.com/tidb/v8.5/release-8.5.4/) to [v8.5.5](https://docs.pingcap.com/tidb/v8.5/release-8.5.5/). diff --git a/tidb-cloud/tidb-cloud-support.md b/tidb-cloud/tidb-cloud-support.md index 00399e77e77b0..cbc1255db1db1 100644 --- a/tidb-cloud/tidb-cloud-support.md +++ b/tidb-cloud/tidb-cloud-support.md @@ -39,8 +39,10 @@ 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 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**.