Permissions

Background

If you need to assign different permissions to personnel in your enterprise to access your BMSs, 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 resources. For example, if you want some software developers in your enterprise to use BMSs but do not want them to delete BMSs or perform any other high-risk operations, you can create IAM users and grant permission to use BMSs but not permission to delete them.

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, see IAM Service Overview.

BMS 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.

BMS 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-2) in the specified regions (for example, AP-Bangkok), the users only have permissions for BMSs in the selected projects. If you set Scope to All resources, users have permissions for BMSs in all region-specific projects. When accessing BMSs, the users need to switch to the authorized region.

You can grant user 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 BMSs of a certain type. A majority of fine-grained policies contain permissions for specific APIs. For the API actions supported by BMS, see Permissions and Supported Actions.

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

Table 2 lists the common operations supported by system-defined permissions for BMS.

Helpful Links

• IAM Service Overview
• Permissions Policies and Supported Actions