Permissions Management

If you need to assign different permissions to personnel in your enterprise to access your CPH resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to securely access your Huawei Cloud resources.

With IAM, you can create IAM users and assign permissions to control their access to specific Huawei Cloud resources. For example, if you want some software developers in your enterprise to view CPH resources but do not want them to restart cloud phones or perform any other high-risk operations, you can create IAM users and grant permission to view CPH resources but not permission to restart cloud phones.

If your Huawei Cloud account does not require individual IAM users for permissions management, you can skip this section.

IAM is a free service. You only pay for the resources in your account. For more information about IAM, see What Is IAM?

CPH Permissions

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 cloud services based on the permissions they have been assigned.

CPH is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects (for example, ap-southeast-1) in the specified regions (for example, CN-Hong Kong), the users only have permissions for CPH in the selected projects. If you set Scope to All resources, the users have permissions for CPH in all region-specific projects. When accessing CPH, the users need to switch to the authorized region.

You can grant permissions by using roles and policies.

Roles: A coarse-grained authorization strategy provided by IAM to assign permissions based on users' job responsibilities. Only a limited number of service-level roles are available for authorization. Huawei Cloud services depend on each other. When you grant permissions using roles, you also need to attach any existing role dependencies. Roles are not ideal for fine-grained authorization and least privilege access.
Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant users only permission to manage ECSs of a certain type. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by CPH, see Permissions and Supported Actions.

Table 1 lists all the system-defined permissions for CPH.

**Table 1** System-defined permissions for CPH
Role/Policy Name	Description	Type	Dependencies
CPH Administrator	Administrator permissions for CPH. Users with these permissions can perform all operations on cloud phone servers.	System-defined role	For servers that use custom networks, the VPC FullAccess permissions are required. Select dependent roles in the same project.
CPH User	Read-only permissions for CPH. Users with these permissions can only view data about cloud phone servers.	System-defined role	Dependent on the Tenant Guest policy.
CPH FullAccess	Users with these permissions can perform all operations defined in the actions supported by CPH.	System-defined policy	If the permissions are not supported by CPH actions, you can use roles to assign permissions.
CPH ReadOnlyAccess	Users with these permissions can only view data about cloud phone servers.	System-defined policy	If the permissions are not supported by CPH actions, you can use roles to assign permissions.
CPH NotSupportEnterpriseAccess	Enterprise project fine-grained actions that are not supported by CPH. CPH users who want to use enterprise projects and use all CPH functions need to obtain the permissions in the CPH FullAccess policy (granted By Enterprise Project) and the permissions in the CPH NotSupportEnterpriseAccess policy (granted By IAM Project).	System-defined policy	If the permissions are not supported by CPH actions, you can use roles to assign permissions.
CPH AgencyDependencyAccess	Fine-grained actions on which CPH depends to create cloud phone servers.	System-defined policy	If the permissions are not supported by CPH actions, you can use roles to assign permissions.

Table 2 lists the common operations supported by each CPH system role. Choose proper system roles according to this table.

**Table 2** Relationship between common operations and system roles
Description	CPH Administrator	CPH User	CPH FullAccess	CPH ReadOnlyAccess	CPH NotSupportEnterpriseAccess
Purchasing a cloud phone server	√	×	√	×	×
Deleting a cloud phone server	√	×	√	×	×
Migrating workloads from a cloud phone server to another server	√	×	√	×	×
Querying cloud phone servers	√	√	√	√	×
Querying details of a cloud phone server	√	√	√	√	×
Querying cloud phone server flavors	√	√	√	√	√
Modifying the name of a cloud phone server	√	×	√	×	×
Changing the flavor of a cloud phone server	√	×	√	×	×
Restarting a cloud phone server	√	×	√	×	×
Pushing a shared storage file	√	×	√	×	×
Querying a shared storage file	√	√	√	√	×
Deleting a shared storage file	√	×	√	×	×
Pushing a shared application	√	×	√	×	×
Deleting a shared application	√	×	√	×	×
Changing a key pair	√	×	√	×	×
Querying encoding servers	√	√	√	√	×
Restarting an encoding server	√	×	√	×	×
Querying the bandwidth used by a cloud phone	√	√	√	√	√
Modifying a shared bandwidth	√	×	√	×	√
Querying cloud phones	√	√	√	√	×
Querying details of a cloud phone	√	√	√	√	×
Querying cloud phone flavors	√	×	√	×	√
Resetting cloud phones	√	×	√	×	×
Restarting a cloud phone	√	×	√	×	×
Stopping a cloud phone	√	×	√	×	×
Editing the name of a cloud phone	√	×	√	×	×
Updating cloud phone attributes	√	×	√	×	×
Exporting data of multiple cloud phones	√	×	√	×	×
Restoring cloud phone data	√	×	√	×	×
Diverting cloud phone traffic	√	×	√	×	×
Expanding the disk capacity of multiple cloud phones	√	×	√	×	×
Obtaining information about the cloud phones to be accessed	√	√	√	√	×
Running the asynchronous ADB shell commands	√	×	√	×	×
Running the synchronous ADB shell commands	√	×	√	×	×
Querying the execution status of a task	√	√	√	√	√
Querying the execution statuses of all tasks	√	√	√	√	√
Batch adding tags	√	×	√	×	×
Batch deleting tags	√	×	√	×	×
Querying resources by tag	√	√	√	√	×
Querying resource tags	√	√	√	√	×
Querying tags of CPH resources in a project	√	√	√	√	×
Querying cloud phone images	√	√	√	√	√
Deleting a cloud phone image	√	×	√	×	×
Sharing a cloud phone image	√	×	√	×	×
Querying users with whom you shared a cloud phone image	√	√	√	√	×
Stopping sharing of a cloud phone image	√	×	√	×	×
Querying AZs	√	√	√	√	√
Querying subnets	√	√	√	√	√
Querying VPC peering connections	√	√	√	√	√
Deleting a VPC peering connection	√	×	√	×	×
Adding a VPC peering connection	√	×	√	×	×
Exporting details of multiple cloud phones	√	×	√	×	×
Creating an agency	√	×	√	×	√
Checking an agency	√	×	√	×	√