Help Center/ Cloud Service Engine/ User Guide/ Using IAM to Grant Access to CSE/ Using IAM Identity Policies to Grant Access to CSE
Updated on 2026-01-15 GMT+08:00
View PDF
Share

Using IAM Identity Policies to Grant Access to CSE

Identity Policy-Based AuthorizationPermissions provided by Identity and Access Management (IAM) lets you control access to CSE. 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 CSE resources.
  • Grant users only the permissions required to perform a given task based on their job responsibilities.
  • Entrust a Huawei Cloud account or cloud service to perform efficient O&M on your CSE 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 system-defined permissions in Permissions for CSE. To grant permissions for other services, learn about all system-defined permissions supported by IAM.

Process Flow

Figure 1 Process of granting CSE permissions using role/policy-based authorization
  1. On the IAM console, create an IAM user or create a user group.

  2. Attach a system-defined identity policy (SWRReadOnlyPolicy as an example) to the user or user group.

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

    In the authorized region, perform the following operations:

    • Choose Service List > Cloud Service Engine. Then click Buy ServiceComb Engine on the CSE console. If the ServiceComb engine fails to be purchased, the CSEReadOnlyPolicy (assume that only this permission granted) is in effect.
    • Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the CSEReadOnlyPolicy policy is in effect.

Example Custom Policies

You can create custom policies to supplement the system-defined policies of CSE. For details about actions supported in custom identity policies, see Actions Supported by Identity Policy-based Authorization.

To create a custom identity 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 supported recourse types and condition keys, see Actions Supported by Identity Policy. The following lists examples of common CSE custom policies.

Example: An IAM user is prohibited to create a microservice engine.

{
    "Version": "5.0",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "cse:*:*",
                "eps:enterpriseProjects:list"
            ]
        },
        {
            "Effect": "Deny",
            "Action": [
                "cse:engine:create"
            ]
        }
    ]
}