Using IAM Identity Policies to Grant Access to CloudPond

Prerequisites

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

Process Flow

Figure 1 Process of granting CloudPond permissions using identity policy-based authorization

1. On the IAM console, create an IAM user or create a user group.

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

   Assign the permissions defined in the system-defined identity policy IESReadOnlyPolicy 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 > CloudPond. Then click Register Edge Site on the CloudPond console. If a message appears indicating that you have insufficient permissions to perform the operation, the IESReadOnlyPolicy 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 IESReadOnlyPolicy policy is in effect.

Example Custom Identity Policies

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

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 grammar.
• 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 "Actions Supported by Identity Policy-based Authorization" in the CloudPond API Reference. The following provides examples of custom CloudPond identity policies.

• Example 1: Grant permission to register and delete an edge site.

  {
      "Version": "5.0",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "ies:edgeSite:create",
                  "ies:edgeSite:delete"
              ]
          }
      ]
  }

• Example 2: Create a custom identity policy containing multiple actions.
  A custom identity policy can contain the actions of one or more services. Example identity policy containing multiple actions:

  {
      "Version": "5.0",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "ies:edgeSite:create",
                  "ies:edgeSite:delete"
              ]
          },
          {
              "Effect": "Allow",
              "Action": [
                  "evs:volumes:create",
                  "evs:volumes:list"
              ]
          },
          {
              "Effect": "Allow",
              "Action": [
                  "ecs:cloudServers:createServers",
                  "ecs:cloudServers:listServersDetails"
              ]
          }
      ]
  }