This chapter describes fine-grained permissions management for your BMS. If your HUAWEI CLOUD account does not need individual IAM users, then you may skip over this chapter.
A policy is a set of permissions defined in JSON format. By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on BMS based on the permissions. For details about the policy syntax and example policies, see Syntax of Fine-Grained Policies in Bare Metal Server User Guide.
There are fine-grained policies and role-based access control (RBAC) policies. An RBAC policy consists of permissions for an entire service. Users in a group with such a policy assigned are granted all of the permissions required for that service. A fine-grained policy consists of API-based permissions for operations on specific resource types. Fine-grained policies, as the name suggests, allow for more fine-grained control than RBAC polices.
- BMS only supports fine-grained policies.
- Fine-grained policies are currently available for open beta testing. You can apply to use the fine-grained access control function free of charge. For more information, see Applying for Fine-Grained Access Control.
A HUAWEI CLOUD 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 that have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user queries BMSs using an API, the user must have been granted permissions that allow the bms:servers:list action.
Operations supported by a fine-grained policy are specific to APIs. The following describes the headers of the action tables provided in this chapter:
- Permissions: Defined by actions in a custom policy.
- Actions: Added to a custom policy to control permissions for specific operations.
- Authorization Scope: A custom policy can be applied to IAM projects or enterprise projects or both. 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 Project. For details about the differences between IAM and enterprise projects, see Differences Between IAM Projects and Enterprise Projects.
- APIs: REST APIs that can be called in a custom policy.
- The actions and scopes of native OpenStack APIs of BMS are the same as those of ECS. For details, see Permissions Policies and Supported Actions in Elastic Cloud Server API Reference.
- When customizing a BMS user policy in IAM, add the ecs:*:get and ecs:*:list permissions. Otherwise, functions on some pages cannot work properly.
- High-speed networks and user-defined networks do not support enterprise projects. To use the two functions, use the primary account.
- The vpc:ports:get permission must be assigned to the sub-account of an enterprise project. Otherwise, the EIP and security group cannot be properly displayed on the BMS details page.