tidb-cloud: add Azure Blob Storage access configuration for Dedicated #19090
Conversation
Implement instructions for configuring Azure Blob Storage access in TiDB Cloud Dedicated. This change supports the new Import feature for TiDB Cloud Dedicated on Azure, allowing users to import data from Azure Blob Storage containers. Those instructions are consistent with tidb-cloud/serverless-external-storage.md (branch release-7.5) The instructions cover: - Accessing the Azure Storage account - Creating a service SAS token with appropriate permissions
ti-chi-bot
bot
added
missing-translation-status
|
@qiancai We may also alter the Markdown file name to make it consistent with what Serverless have today: |
Yes, I completely agree. I’ll rename the file and add the alias. |
qiancai
added
area/tidb-cloud
ti-chi-bot
bot
removed
the
missing-translation-status
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@alastori, would you please involve a tech reviewer for this PR? Thanks. |
qiancai
added
the
needs-cherry-pick-release-7.5
There was a problem hiding this comment.
Allowed Permissions should be Read + List
There was a problem hiding this comment.
updated in 4f1caf3 (#19090)
There was a problem hiding this comment.
It is not recommended to change the name of the document, as it will be referenced in multiple places on the page
There was a problem hiding this comment.
In this PR, we’ve added an alias for the old doc link as follows so that anyone clicking the old doc link will be redirected to the new link. However, it’s still recommended to update the link in the Cloud console for consistency after the changes in this PR take effect on the docs website.
| > TiDB Cloud does not store your SAS token. It is recommended that you revoke or delete the SAS token after the import is complete to ensure the security of your Azure Blob Storage. | ||
|
|
||
| Remember to test the connection and permissions before starting your data import to ensure TiDB Cloud Dedicated can access the specified Azure Blob container and files. |
There was a problem hiding this comment.
| > TiDB Cloud does not store your SAS token. It is recommended that you revoke or delete the SAS token after the import is complete to ensure the security of your Azure Blob Storage. | |
| Remember to test the connection and permissions before starting your data import to ensure TiDB Cloud Dedicated can access the specified Azure Blob container and files. | |
| > - Before starting your data import, it is recommended that you test the connection and permissions to ensure that TiDB Cloud Dedicated can access the specified Azure Blob container and files. | |
| > - TiDB Cloud does not store your SAS token. After the import is complete, it is recommended that you revoke or delete the SAS token to ensure the security of your Azure Blob Storage. |
| 1. In the **Allowed services** section, choose the **Blob** service. | ||
| 2. In the **Allowed Resource types** section, choose **Container** and **Object**. | ||
| 3. In the **Allowed permissions** section, choose the permissions as needed. For example, importing data to a TiDB Cloud Dedicated cluster needs the **Read** and **List** permissions. | ||
| 4. Adjust **Start and expiry date/time** as needed. For security reasons, it's recommended to set an expiration date that aligns with your data import timeline. |
There was a problem hiding this comment.
| 4. Adjust **Start and expiry date/time** as needed. For security reasons, it's recommended to set an expiration date that aligns with your data import timeline. | |
| 4. Adjust **Start and expiry date/time** as needed. For security reasons, it is recommended to set an expiration date that aligns with your data import timeline. |
|
@jusong: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
qiancai
added
the
do-not-merge/hold
What is changed, added or deleted? (Required)
Added instructions for configuring Azure Blob Storage access in TiDB Cloud Dedicated (page Configure External Storage Access).
Those instructions are consistent with
tidb-cloud/serverless-external-storage.md (branch release-7.5)
The instructions cover:
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?