Help Center/ Application Service Mesh/ User Guide/ Using IAM to Grant Access to ASM/ Using IAM Roles or Policies to Grant Access to ASM
Updated on 2026-06-25 GMT+08:00
View PDF
Share

Using IAM Roles or Policies to Grant Access to ASM

To manage role-based and policy-based access control for your ASM resources, use Identity and Access Management (IAM). 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 ASM 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 ASM resources.

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

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

Prerequisites

Before assigning permissions to user groups, learn about the available ASM permissions. For details about system permissions supported by ASM, see Role/Policy-based Permissions. To grant permissions for other services, learn about all system-defined permissions supported by IAM.

Process Flow

Figure 1 Process of granting ASM permissions using role/policy-based authorization
  1. On the IAM console, create a user group and assign permissions to it.

    Create a user group on the IAM console, and assign the ASM ReadOnlyAccess permissions to the group.

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

    On the IAM console, create a user and add it to the user 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 > Application Service Mesh. Click Buy Mesh on the ASM console. If a message appears indicating that you have insufficient permissions to perform the operation, the ASM ReadOnlyAccess policy is in effect.
    • Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the ASM ReadOnlyAccess policy is in effect.

Example Custom Policies

You can create custom policies to supplement the system-defined policies of ASM. For details about actions supported in custom policies, see 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 ASM custom policies.

  • Example 1: Grant permissions to create service meshes. 
    {
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "asm:mesh:create"
            ]
        }
    ]
}
  • Example 2: Grant permissions to deny service mesh 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.

    {
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Deny",
            "Action": [
                "asm:mesh:createGateway"
            ]
        }
    ]
}
  • Example 3: Create a custom policy containing multiple actions.

    A custom policy can contain the actions of one or multiple services that are of the same type (global or project-level). Example policy containing actions of multiple services:

    {
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "cce:cluster:create"
                "asm:mesh:create"
            ]
        }
    ]
}