Help Center/ Data Replication Service/ Preparations/ Using IAM to Grant Access to DRS/ Using IAM Roles or Policies to Grant Access to DRS
Updated on 2025-12-18 GMT+08:00
View PDF
Share

Using IAM Roles or Policies to Grant Access to DRS

System-defined permissions in Role/Policy-based Authorization provided by Identity and Access Management (IAM)Identity and Access Management (IAM) let you control access to DRS. With IAM, you can:
  • Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing DRS resources.
  • Grant users only the permissions required to perform a given task based on their job responsibilities.
  • Entrust a Huawei Cloud account or a cloud service to perform efficient O&M on your DRS resources.

If your Huawei Cloud account meets your permissions requirements, you can skip this section.

Figure 1 shows the process flow of role-based authorization.

Prerequisites

Before granting permissions to user groups, learn about system-defined permissions in Role/Policy-based Permissions Management for DRS. To grant permissions for other services, learn about all system-defined permissionspermissions supported by IAM.

Process Flow

Figure 1 Process of granting DRS permissions using role/policy-based authorization
  1. On the IAM console, create a user group and grant it permissions (DRS Administrator as an example).

    Create a user group on the IAM console, and assign the DRS Administrator policy to the group.

  2. Create an IAM user and add it to the created user group.

    Create a user on the IAM console and add the user to the group created in 1.

  3. Log in as the IAM user and verify permissions.

    In the authorized region, perform the following operations:

    Choose Service List > Data Replication Service. Then click Create Migration Task on the DRS console. If a migration task (assume that there is only the DRS Administrator permission) is created, the DRS Administrator policy is in effect.

Example Custom Policies

You can create custom policies to supplement the system-defined policies of DRS. For details about actions supported in custom policies, see Data Replication Service API Reference > "Permissions Policies and Supported Actions" > "Actions Supported by Policy-based Authorization".

To create a custom policy, choose either visual editor or JSON.

  • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy grammar.
  • JSON: Create a JSON policy or edit an existing one.

For details, see Creating a Custom Policy. The following lists examples of common DRS custom policies.

  • Example 1: Grant permission to create DRS instances. 
    {
	"Version": "1.1",
	"Statement": [{
                "Action": ["drs:migrationJob:create"],
		"Effect": "Allow"
	}]
}
  • Example 2: Grant permission to deny DRS instance deletion.

    A policy with only "Deny" permissions must be used together with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

    Assume that you want to grant the permissions of the DRS FullAccess policy to a user but want to prevent them from deleting DRS instances. You can create a custom policy for denying DRS instance deletion, and attach this policy together with the DRS FullAccess policy to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on DRS instances excepting deleting them. Example policy denying DRS instance deletion:

    {
	"Version": "1.1",
	"Statement": [{
		"Action": ["drs:migrationJob:delete"],
		"Effect": "Deny"
	}]
}