Help Center/ Distributed Cache Service/ User Guide/ Using IAM to Grant Access to DCS/ Using IAM Identity Policies to Grant Access to DCS
Updated on 2025-11-12 GMT+08:00

Using IAM Identity Policies to Grant Access to DCS

System-defined permissions in Identity Policy-based Authorization provided by Identity and Access Management (IAM) let you control access to DCS resources. With IAM, you can:

  • Create IAM users or user groups for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing DCS 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 DCS resources.

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

Figure 1 shows the process flow of identity policy-based authorization.

Prerequisites

Before granting permissions, learn about Identity Policy-based Authorization for DCS. To grant permissions for other services, learn about all system-defined permissions supported by IAM.

Process Flow

Figure 1 Process of granting DCS permissions
  1. On the IAM console, create an IAM user or create a user group.

  2. Attach a system-defined identity policy.

    Assign the permissions defined in the system-defined identity policy DCSReadOnlyAccessPolicy to the user or group, or attach the system-defined identity policy to it.

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

    In the authorized region, perform the following operations:

    • Choose Service List > Distributed Cache Service. Then click Buy DCS Instance on the DCS console. If a message appears indicating that you have insufficient permissions to perform the operation, the DCSReadOnlyAccessPolicy policy is in effect.
    • Choose any other service in Service List. If a message appears indicating that you have insufficient permissions to access the service, the DCSReadOnlyAccessPolicy has already taken effect.

Example Custom Identity Policies

You can create custom identity policies to supplement the system-defined identity policies of DCS. For details about actions supported in custom identity policies, see Distributed Cache Service API Reference > "Permissions and Supported Actions" > "Actions Supported by Identity 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 syntax.
  • JSON: Create a JSON policy or edit an existing one.

For details, see Creating a Custom Identity Policy and Attaching It to a Principal.

When creating a custom identity policy, use the Resource element to specify the resources the identity policy applies to and use the Condition element (service-specific condition keys) to control when the identity policy is in effect. For details about the supported resource types and condition keys, see Distributed Cache Service API Reference > "Permissions and Supported Actions" > "Actions Supported by Identity Policy-based Authorization". The following lists examples of common DCS custom identity policies.

  • Example 1: Grant permission to create and delete vaults.
    {
        "Version": "5.0",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "dcs:instance:create",
                    "dcs:instance:delete"
                ]
            }
        ]
    }
  • Example 2: Defining permissions for multiple services in a policy

    A custom policy can contain the actions of multiple services. The following is an example policy containing actions of multiple services:

    {
        "Version": "5.0",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "dcs:instance:create",
                    "dcs:instance:delete"
                ]
            },
            {
                "Effect": "Allow",
                "Action": [
                    "ecs:cloudServers:createServers",
                    "ecs:cloudServers:deleteServers"
                ]
            }
        ]
    }