Permissions Management

If you need to assign different permissions to employees in your enterprise to access your HSS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your HUAWEI CLOUD resources.

With IAM, you can use your HUAWEI CLOUD account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use HSS resources but must not delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using HSS resources.

If your HUAWEI CLOUD account does not need individual IAM users for permissions management, then you may skip over this chapter.

IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see What Is IAM.

HSS Permissions

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.

HSS is a project-level service deployed and accessed in specific physical regions. To assign HSS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing HSS, the users need to switch to a region where they have been authorized to use cloud services.

You can grant users permissions by using roles and policies.

Roles: A coarse-grained authorization mechanism provided by IAM to define permissions based on users' job responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you also need to assign other roles that the permissions depend on to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
Policies: A fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant HSS users only the permissions for managing a certain type of resources. Most policies define permissions based on APIs.

Table 1 lists more details.

**Table 1** System-defined permissions supported by HSS
Role/Policy Name	Description	Role/Policy Type	Dependency
HSS Administrator	HSS administrator, who has all permissions of HSS.	System-defined role	This role depends on the Tenant Guest role. Tenant Guest: a global role, which must be assigned in the Global project To purchase HSS protection quotas, you must have the ECS ReadOnlyAccess and BSS Administrator roles. ECS ReadOnlyAccess: read-only access permission for the ECS. This is a system policy. BSS Administrator: a system role, which is the administrator of the billing center (BSS) and has all permissions for the service.
HSS FullAccess	Full permissions for HSS	System-defined policy	To purchase HSS protection quotas, you must have the BSS Administrator role. BSS Administrator: a system role, which is the administrator of the billing center (BSS) and has all permissions for the service.
HSS ReadOnlyAccess	Read-only permissions for HSS	System-defined policy	None