Introduction to Permissions Policies and Supported Actions

Updated on 2023-06-29 GMT+08:00

View PDF

This section describes fine-grained permissions management for your CCM. If your account does not need individual IAM users, then you may skip over 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.

Permissions are classified into based on the authorization granularity. 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.

NOTE:

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

An account has all of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned. 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 successfully. For example, if an IAM user queries ECSs using an API, the user must have been granted permissions that allow the ecs:servers:list action.

Supported Actions

CCM provides system-defined policies that can be directly used in IAM. 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:

Permission: A statement in a policy that allows or denies certain operations.
APIs: REST APIs that can be called in a custom policy
Actions: Added to a custom policy to control permissions for specific operations.
Dependent actions: When assigning an action to users, you also need to assign dependent permissions for that action to take effect.
IAM projects or enterprise projects: Scope of users a permission is granted to. Policies that contain actions supporting both IAM and enterprise projects can be assigned to user groups and take effect in both IAM and Enterprise Management. Policies that only contain actions supporting IAM projects can be assigned to user groups and only take effect for IAM. Such policies will not take effect if they are assigned to user groups in Enterprise Management.
NOTE:

√: supported; x: not supported

CCM supports the following actions that can be defined in custom policies:

Parent topic: Permissions and Supported Actions

Previous topic: Permissions and Supported Actions

Next topic: Private Certificate Authority (PCA)