-
Notifications
You must be signed in to change notification settings - Fork 680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tidb-cloud: add Azure Blob Storage access configuration for Dedicated #19090
Open
alastori
wants to merge
3
commits into
pingcap:master
Choose a base branch
from
alastori:update-configure-azure-blob-storage-access
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
@@ -1,6 +1,7 @@ | ||||||||||||
--- | ||||||||||||
title: Configure External Storage Access for TiDB Cloud Dedicated | ||||||||||||
summary: Learn how to configure Amazon Simple Storage Service (Amazon S3) access and Google Cloud Storage (GCS) access. | ||||||||||||
aliases: ['/tidb-cloud/config-s3-and-gcs-access'] | ||||||||||||
--- | ||||||||||||
|
||||||||||||
# Configure External Storage Access for TiDB Cloud Dedicated | ||||||||||||
|
@@ -221,3 +222,33 @@ To allow TiDB Cloud to access the source data in your GCS bucket, you need to co | |||||||||||
![Get bucket URI](/media/tidb-cloud/gcp-bucket-uri02.png) | ||||||||||||
|
||||||||||||
7. In the TiDB Cloud console, go to the **Data Import** page where you get the Google Cloud Service Account ID, and then paste the GCS bucket gsutil URI to the **Bucket gsutil URI** field. For example, paste `gs://tidb-cloud-source-data/`. | ||||||||||||
|
||||||||||||
## Configure Azure Blob Storage access | ||||||||||||
|
||||||||||||
To allow TiDB Cloud Dedicated 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: | ||||||||||||
|
||||||||||||
1. On the [Azure Storage account](https://portal.azure.com/#browse/Microsoft.Storage%2FStorageAccounts) page, click your storage account to which the container belongs. | ||||||||||||
|
||||||||||||
2. On your **Storage account** page, click **Security+network** in the left navigation pane, and then click **Shared access signature**. | ||||||||||||
|
||||||||||||
![sas-position](/media/tidb-cloud/dedicated-external-storage/azure-sas-position.png) | ||||||||||||
|
||||||||||||
3. On the **Shared access signature** page, create a service SAS token with the necessary permissions as follows. For more information, see [Create a service SAS token](https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview). | ||||||||||||
|
||||||||||||
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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||
5. You can keep the default values for other settings. | ||||||||||||
|
||||||||||||
![sas-create](/media/tidb-cloud/dedicated-external-storage/azure-sas-create.png) | ||||||||||||
|
||||||||||||
4. Click **Generate SAS and connection string** to generate the SAS token. | ||||||||||||
|
||||||||||||
5. Copy the generated **SAS Token**. You will need this token string when configuring the data import in TiDB Cloud. | ||||||||||||
|
||||||||||||
> **Note:** | ||||||||||||
> | ||||||||||||
> 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. | ||||||||||||
Comment on lines
+252
to
+254
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.