Permissions Policies and Supported Actions

This section describes fine-grained permissions management for your LTS. If your account does not require IAM users, you can skip this section.

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

You can grant users permissions by using roles and policies. Roles are a type of coarse-grained authorization mechanism that defines service-level permissions based on user 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.

You can use policies to allow or deny access to specific APIs.

An account has all of the permissions required to call all APIs, but IAM users must be assigned the required permissions. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API. 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. You can also create custom policies and use them to supplement system-defined policies, implementing more refined access control. Operations supported by policies are specific to APIs. The following are basic concepts related to policies:

• Permissions: Statements in a policy that allow or deny certain operations.
• APIs: REST APIs that can be called by users with the required permissions.
• Actions: Specific operations that are allowed or denied.
• Related actions: Actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the related actions.
• IAM or enterprise projects: Type of projects for which permissions can be granted. Policies that contain actions for both IAM and enterprise projects take effect for both IAM and Enterprise Management. Policies that only contain actions for IAM projects take effect only for IAM.

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