Using IAM Roles or Policies to Grant Access to AOM

Prerequisites

Before granting permissions to a user group, learn about the AOM system-defined permissions in Role/Policy-based Authorization. To grant permissions for other services, learn about Service Authorization Reference.

Process Flow

Figure 1 Process for granting AOM permissions

1. On the IAM console, create a user group and grant it permissions (AOM ReadOnlyAccess as an example).
2. Create an IAM user and add it to the created user group
3. Log in as an IAM user and verify permissions.

Example Custom Policies

You can create custom policies to supplement the system-defined policies of AOM. For details about the 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 syntax.
• JSON: Create a JSON policy or edit an existing one.

For details, see Creating a Custom Policy. The following provides examples of common AOM custom policies.

• Example 1: Grant permission to create alarm rules.

  {
      "Version": "1.1",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "aom:alarmRule:create"
              ]
          }
      ]
  }

• Example 2: Grant permission to deny deletion of application discovery rules.

  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.

  Assume that you want to grant the permissions of the AOM FullAccess policy to a user but want to prevent them from deleting application discovery rules. You can create a custom policy for denying deletion of such rules, and attach this policy together with the AOM FullAccess policy to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on AOM excepting deleting application discovery rules. Example policy denying deletion of application discovery rules:

  {
        "Version": "1.1",
        "Statement": [
              {
      "Effect": "Deny",
                    "Action": [
                          "aom:discoveryRule:delete"
                    ]
              }
        ]
  }

• 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 (project-level). Example policy containing multiple actions:

  {
          "Version": "1.1",
          "Statement": [
                  {
                          "Effect": "Allow",
                          "Action": [
                                  "aom:*:list",
                                  "aom:*:get",
                                  "apm:*:list",
                                  "apm:*:get"
                          ]
                  },
                  {
                           "Effect": "Allow",
                           "Action": [
                                   "cce:cluster:get",
                                   "cce:cluster:list",
                                   "cce:node:get",
                                   "cce:node:list"
                          ]
                  }
          ]
  }