Help Center/ ServiceStage/ User Guide/ Using IAM to Grant Access to ServiceStage/ Using IAM Identity Policies to Grant Access to ServiceStage
Updated on 2025-11-11 GMT+08:00
View PDF
Share

Using IAM Identity Policies to Grant Access to ServiceStage

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

Process Flow

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

    Create a user or user group on the IAM console.

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

    Assign the permissions defined in the system-defined identity policy ServiceStageReadOnlyPolicy 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:

    1. Choose Service List > ServiceStage > Application Management.
    2. Click Create Application. If a message appears indicating that you have insufficient permissions to perform the operation, the ServiceStageReadOnlyPolicy policy is in effect.

Example Custom Identity Policies

You can create custom identity policies to supplement the system-defined identity policies of ServiceStage. For details about actions supported in custom identity policies, see 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, see Actions Supported by Identity Policy-based Authorization. The following lists examples of common ServiceStage custom identity policies.

  • Example 1: Forbid IAM users to create applications. 
    {
    "Version": "5.0",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "servicestage:*:*",
                "eps:enterpriseProjects:list"
            ]
        },
        {
            "Effect": "Deny",
            "Action": [
                "servicestage:app:createApplication"
            ]
        }
    ]
}
  • Create a custom identity policy containing multiple actions.

    A custom identity policy can contain the actions of one or more services. Example:

    {
    "Version": "5.0",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "servicestage:environment:create"
                "eps:enterpriseProjects:list"
            ]
        },
        {
            "Effect": "Deny",
            "Action": [
                "cce:node:list"
            ]
        }
    ]
}