Permissions and Supported Actions

You can use Identity and Access Management (IAM) for fine-grained permissions management of your Huawei Cloud UCS. If your HUAWEI ID does not need individual IAM users, you can skip this chapter.

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 IAM users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned. For details about policy syntax and example policies, see Permissions.

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.

Your account has all the permissions required to call all APIs. If you use IAM users in your account to call an API, the IAM users must be granted 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 wants to call an API to query ECSs, the user must be granted the permissions allowing for action ecs:servers:list.

Supported Actions in IAM

UCS 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/Enterprise projects: the authorization scope of a custom policy. A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions for both IAM and enterprise projects can be used and applied for both IAM and Enterprise Management. Policies that contain actions only for IAM projects can be used and applied to IAM only. For details about the differences between IAM and enterprise management, see What Are the Differences Between IAM and Enterprise Management?
IAM projects/Enterprise projects: the authorization scope of a custom policy. A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions for both IAM and enterprise projects can be used and applied for both IAM and Enterprise Management. Policies that contain actions only for IAM projects can be used and applied to IAM only. For details about the differences between IAM and enterprise management, see What Are the Differences Between IAM and Enterprise Management?

√: supported; x: not supported

Huawei Cloud UCS supports the following actions in custom policies:

**Table 1** UCS cluster actions
Permission	API	Action	IAM Project	Enterprise Project
Obtaining the cluster list	GET /v1/clusters	ucs:clusters:list	√	√
Obtaining a cluster	GET /v1/clusters/{clusterid}	ucs:clusters:get	√	√
Registering a cluster	POST /v1/cluster	ucs:clusters:create	√	√
Updating a cluster	PUT /v1/clusters/{clusterid}	ucs:clusters:update	√	√
Deleting a cluster	DELETE /v1/clusters/{clusterid}	ucs:clusters:delete	√	√
Obtaining cluster access information	GET /v1/clusters/{clusterid}/accessinfo	ucs:clusters:create	√	√
Activating a cluster	PUT /v1/clusters/{clusterid}/activation	ucs:clusters:update	√	√
Associating a cluster with permission policies	PUT /v1/clusters/{clusterid}/associatedrules	ucs:clustergroups:update	√	√
Obtaining the CCE cluster list of a tenant	GET /v1/managedclusters	ucs:clusters:list	√	√

**Table 2** Fleet actions
Permission	API	Action	IAM Project	Enterprise Project
Adding a cluster to a fleet	POST /v1/clusters/{clusterid}/join	ucs:clusters:update	√	√
Removing a cluster from a fleet	POST /v1/clusters/{clusterid}/unjoin	ucs:clusters:update	√	√
Creating a fleet	POST /v1/clustergroups	ucs:clustergroups:create	√	√
Deleting a fleet	DELETE /v1/clustergroups/{clustergroupid}	ucs:clustergroups:delete	√	√
Obtaining a fleet	GET /v1/clustergroups/{clustergroupid}	ucs:clustergroups:get	√	√
Adding clusters to a fleet	PUT /v1/clustergroups/{clustergroupid}/associatedclusters	ucs:clustergroups:update	√	√
Updating fleet description	PUT /v1/clustergroups/{clustergroupid}/description	ucs:clustergroups:update	√	√
Updating permission policies associated with a fleet	PUT /v1/clustergroups/{clustergroupid}/associatedrules	ucs:clustergroups:update	√	√
Updating the zone associated with the federation of a fleet	PUT /v1/clustergroups/{clustergroupid}/associatedzones	ucs:clustergroups:update	√	√
Obtaining the fleet list	GET /v1/clustergroups	ucs:clustergroups:list	√	√
Enabling cluster federation	POST /v1/clustergroups/{clustergroupid}/federations	ucs:clustergroups:create	√	√
Disabling cluster federation	DELETE /v1/clustergroups/{clustergroupid}/federations	ucs:clustergroups:delete	√	√
Querying federation enabling progress	GET /v1/clustergroups/{clustergroupid}/federations/progress	ucs:clustergroups:get	√	√
Creating a federation connection and downloading kubeconfig	POST /v1/clustergroups/{clustergroupid}/cert	ucs:clustergroups:get	√	√
Creating a federation connection	POST /v1/clustergroups/{clustergroupid}/connection	ucs:clustergroups:get	√	√
Downloading federation kubeconfig	POST /v1/clustergroups/{clustergroupid}/kubeconfig	ucs:clustergroups:get	√	√

**Table 3** Permissions management actions
Permission	API	Action	IAM Project	Enterprise Project
Creating a permission policy	POST /v1/permissions/rules	ucs:permissionsRules:create	√	√
Obtaining the permission policy list	GET /v1/permissions/rules	ucs:permissionsRules:list	√	√
Deleting a permission policy	DELETE /v1/permissions/rules/{ruleid}	ucs:permissionsRules:delete	√	√
Updating a permission policy	PUT /v1/permissions/rules/{ruleid}	ucs:permissionsRules:update	√	√