Permissions and Supported Actions

You can use Identity and Access Management (IAM) for fine-grained permissions management of your LTS. If your account does not need individual IAM users, you can skip this section.

New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on LTS based on the permissions they have been assigned.

You can grant users permissions by using roles and policies. Roles are provided by IAM to define service-based permissions that match users' job responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

Policy-based authorization is useful if you want to allow or deny the access to an API.

An account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions. The required permissions are determined by the actions supported by the API. Only users with the policies allowing for those actions can call the API successfully. For example, if an IAM user queries log metrics using an API, the user must have been granted permissions that allow the aom:metric:get action.

Supported Actions

LTS provides system-defined policies that can be directly used in IAM. You can also create custom policies to supplement system-defined policies for more refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:

• Permissions: statements in a policy that allow or deny certain operations.
• APIs: REST APIs that can be called by a user who has been granted specific permissions.
• Actions: specific operations that are allowed or denied in a custom policy.
• Dependencies: actions which a specific action depends on. When allowing an action for a user, you also need to allow any existing action dependencies for that user.
• IAM projects: the authorization scope of a custom policy.

The check mark (√) and cross symbol (x) respectively indicate that a permission can be or cannot be granted for the corresponding type of projects.