Permissions Policies and Supported Actions

This chapter describes fine-grained permissions management for your APM. If your account does not need individual IAM users, then you may skip over this chapter.

By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies or roles to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on APM.

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

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, and 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 can call the API successfully. For example, if an IAM user tries to obtain an AK/SK by calling an API, the user must have been granted permissions that allow the apm:apm2AkSk:read action.

Supported Actions

APM 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 common concepts related to policies:

• Permissions: Defined by actions in a custom policy.
• APIs: REST APIs that can be called by a user who has been granted specific 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 an action will take effect. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM. For details about the differences between IAM and enterprise projects, see Differences Between IAM and Enterprise Management.

The check mark (√) and cross symbol (x) indicate that an action takes effect or does not take effect for the corresponding type of projects.

Table 1 Actions

Permission	API	Action	IAM Project	Enterprise Project
Obtaining an AK/SK	GET /v1/apm2/openapi/systemmng/get-ak-sk-list	apm:apm2AkSk:read	√	√
Querying the application list	GET /v1/apm2/openapi/cmdb/business/get-business-list	-	√	√
Obtaining the PodLB address of the master service based on the region name	GET /v1/apm2/openapi/systemmng/get-master-address	-	√	√