Using IAM Roles or Policies to Grant Access to LTS

Prerequisites

Before granting permissions to user groups, learn about system-defined permissions in Role/Policy-based Permissions Management for LTS. To grant permissions for other services, learn about all system-defined permissions supported by IAM.

Process Flow

Figure 1 Process of granting LTS permissions using role/policy-based authorization

1. On the IAM console, create a user group and grant it permissions (LTS ReadOnlyAccess as an example).

   Create a user group on the IAM console and assign the LTS ReadOnlyAccess permission to the group.

2. Create an IAM user and add it to the created 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 > Log Tank Service. On the Log Management page displayed, if you can view LTS data but cannot create log groups, the LTS 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 LTS ReadOnlyAccess policy is in effect.

Example Custom Policies

You can create custom policies to supplement the system-defined policies of LTS. 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 LTS custom policies.

• Example 1: Grant permission to query log groups.

  {
      "Version": "1.1",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "lts:groups:get"
              ]
          }
      ]
  }

• Example 2: Grant permission to deny log group 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.

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

  {
      "Version": "1.1",
      "Statement": [
          {
              "Effect": "Deny",
              "Action": [
                  "lts:groups: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 (global or project-level). Example policy containing multiple actions:

  {
      "Version": "1.1",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "lts:groups:get",
                  "lts:groups:create",
                  "lts:logs:list"
              ]
          },
          {
              "Effect": "Allow",
              "Action": [
                  "ecs:instanceScheduledEvents:list"
              ]
          }
      ]
  }