Actions Supported by Policy-based Authorization

Supported Actions

BMS 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. Administrators can check whether an action supports IAM projects or enterprise projects in the action list. For details about the differences between IAM and enterprise management, see Differences Between IAM and Enterprise Management.

BMS supports the following actions in custom policies:

• Lifecycle management actions, including all of the actions supported by BMS lifecycle management APIs, such as the APIs for creating BMSs and querying BMS details.
• Status management actions, including all of the actions supported by BMS status management APIs, such as the APIs for stopping, restarting, and starting BMSs in a batch.
• Password management actions, including all of the actions supported by BMS password management APIs, such as the API for querying whether BMS passwords can be reset and API for resetting a BMS password.
• Flavor query actions, including all of the actions supported by BMS flavor query APIs, such as the APIs for querying flavor details and extended flavor information.
• NIC management actions, including all of the actions supported by BMS NIC management APIs, such as the API for querying BMS NICs.
• Disk management actions, including all of the actions supported by BMS disk management APIs, such as the APIs for attaching disks to a BMS and detaching disks from a BMS.
• Metadata management actions, including all of the actions supported by BMS metadata management APIs, such as the API for updating BMS metadata.
• Tenant quota management actions, including all of the actions supported by BMS quota management APIs, such as the API for querying tenant quotas.

Action Description

• The actions and scope of native OpenStack APIs for BMS are the same as those for ECS. For details, see Permissions and Supported Actions.
• When customizing a BMS policy in IAM, add the ecs:*:get and ecs:*:list permissions. Otherwise, some functions may not work properly due to insufficient permissions.
• High-speed networks and user-defined networks do not support enterprise projects. You can only use the two types of networks under a primary account.
• The vpc:ports:get permission must be assigned to sub-accounts of enterprise projects. Otherwise, EIPs and security groups cannot be properly displayed on BMS details pages.