This document describes how to use the data migration feature of DTS to perform data migration between the source and target TencentDB instances under different root accounts.
Supported Scope
Data migration from TencentDB for MySQL/MongoDB/PostgreSQL.
Prerequisites
You have created the target database instance.
Notes
This operation involves multiple account information configuration items. The following lists the main configuration logic for easier understanding and configuration.
Data migration direction: Source database (database instance under another account) > target database (database instance under the current account).
The account executing the migration task can be the root account or a sub-account of the target database.
If you use a root account to execute the migration task, before executing the task, ask the root account of the source database to grant the root account of the target database access to the source database.
If you use a sub-account to execute the migration task, before executing the task, ask the root account of the source database to grant the root account of the target database access to the source database with a role, and then ask the root account of the target database to grant the sub-account access to the source database.
Authorizing an Account
To execute the migration task with a root account or a sub-account, follow steps 1–6 or steps 1–11 respectively.
1. Log in to the CAM console with the Tencent Cloud root account of the source database (if the sub-account has CAM and role permissions, you can also log in with the sub-account).
2. Click Role on the left sidebar to enter the Role Management page. Then, click Create Role.
3. On the Select role entity page, select Tencent Cloud Account.
4. On the Enter Role Entity Info page, configure the information and click Next.
Tencent Cloud account: Select Other root account.
Account ID: Enter the Tencent Cloud root account ID of the target database, which can be viewed in Account Info. Even if the target database instance is owned by a sub-account, you still need to enter the root account ID here.
External ID: You can enable it as needed.
Note:
If an external ID is used, record and keep the ID on your own, as it cannot be queried in DTS.
5. On the Configure Role Policy page, select the corresponding policies of DTS and the source database and click Next.
For the DTS policy, select QcloudDTSReadOnlyAccess.
For the corresponding policy of the source database, select the policy of the Tencent Cloud service to which the source database belongs. For example, if the source database is TencentDB for MySQL or PostgreSQL, select QcloudAccessForMySQLRole or QcloudPostgreSQLReadOnlyAccess respectively. Select a policy based on the actual conditions.
6. Configure role tags. Then, on the Review page, set the role name and click Complete.
Note:
Record the configured role name, which needs to be entered when you create the migration task later.
Note:
To execute a migration task with the root account, just follow the steps above; to execute a migration task with a sub-account, you also need to ask the root account to authorize the sub-account as follows:
7. (Optional) Log in to the CAM console with the Tencent Cloud root account of the target database and click Policies on the left sidebar. Then, click Create Custom Policy on the right and select Create by Policy Syntax.
8. (Optional) Select Blank Template and click Next.
9. (Optional) Create a policy and enter the policy name and description as needed. After copying the sample code to the Policy Content, replace the content in the red box with the actual information.
11. (Optional) Click Complete, return to the Policy List page, and click Associate Users/Groups.
12. (Optional) Select the sub-account of the target database instance (i.e., the sub-account executing the migration task) and click OK.
Creating a Migration Task
1. Log in to the DTS console with the Tencent Cloud account of the target database instance.
2. Select Data Migration > Create Migration Task to purchase a migration task.
3. After making the purchase, return to the data migration task list and click Configure in the Operation column to enter the migration task configuration page.
4. On the Set source and target databases page, configure the source and target database information. The following takes data migration between two TencentDB for MySQL instances as an example.
Configure the key parameters for cross-account data migration as follows:
Access Type: Select Database, indicating that the source database is a TencentDB instance.
Cross-/Intra-Account: Select Cross-account.
Peer Account ID: Enter the root account ID of the source database.
External Role ID: This parameter is optional, and its value can be obtained from the previous section. For more information on roles, see Role Overview and Cross-account Access Role.
Note:
After completing the above configuration, select the Region to get the instance list under the source database account. If an error occurs while getting the instances, the configuration may be incorrect, or no authorization has been performed. For more information, see FAQs.
5. On the Set migration options and select migration objects page, set the data migration options, select migration objects, and click Save and Go Next.
6. On the Verify task page, complete the verification. After all check items are passed, click Start Task.
If the verification fails, fix the problem as instructed in Check Item Overview and initiate the verification again.
7. Return to the data migration task list, and you can see that the task has entered the Running status.
FAQs
1. What should I do if the error "role not exist[InternalError.GetRoleError]" is reported when the instance list is pulled across accounts?
Check whether the Peer Account ID (the root account ID of the source database) and Peer Account Role Name (the role name created in step 6 in Authorizing an Account) have been correctly configured.
2. What should I do if the error InternalError:InternalInnerCommonError is reported when the database instance list is obtained?
The policy of the Tencent Cloud service to which the source database belongs hasn't been granted to the role. Grant it as instructed in step 5 in Authorizing an Account.
3. What should I do if the error "you are not authorized to perform operation (sts:AssumeRole), resource (qcs::cam::uin/1xx5:roleName/xxxx) has no permission" is reported when the instance list is pulled across accounts?
Error cause: The account that you use to create the migration task is a sub-account without the sts:AssumeRole permission.
Solution:
Use the root account to create the migration task.
Ask the root account of the target database to authorize the sub-account as instructed in Authorizing an Account and set resource in the policy syntax to the field in blue in the error message.
Yes
No
Was this page helpful?