Updated on 2025-11-06 GMT+08:00

Bare Metal Server (BMS)

IAM provides system-defined identity policies to define common actions supported by cloud services. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM, the Organizations service provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to a principal. They only set the permissions boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM is different from Organizations for access control, see What Are the Differences in Access Control Between IAM and Organizations?

This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.

Actions

Actions are specific operations that are allowed or denied in an identity policy.

  • The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
  • The Resource Type column indicates whether the action supports resource-level permissions.
    • You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
    • If this column includes a resource type, you must specify the URN in the Resource element of your statements.
    • Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.

    For details about the resource types defined by BMS, see Resources.

  • The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
    • If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
    • If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
    • If the Condition Key column of an action is empty (-), the action does not support any condition keys.

    For details about the condition keys defined by BMS, see Conditions.

  • The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.

The following table lists the actions that you can define in identity policy statements for BMS.

Table 1 Actions supported by BMS

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

bms:servers:updateBaremetalServer

Grants permission to modify a BMS.

write

instance*

bms:servers:put

bms:servers:showBaremetalServerInterfaceAttachments

Grants permission to query BMS NICs.

read

instance*

bms:servers:get

bms:servers:resetServerPwd

Grants permission to reset a BMS password with a few clicks.

write

instance*

-

bms:servers:showResetPasswordFlag

Grants permission to check whether BMS passwords can be reset with a few clicks.

read

instance*

bms:servers:get

bms:servers:showWindowsBaremetalServerPwd

Grants permission to obtain Windows BMS passwords.

read

instance*

bms:servers:get

bms:servers:deletePassword

Grants permission to delete Windows BMS passwords.

write

instance*

-

bms:servers:showBaremetalServerVolumeInfo

Grants permission to query EVS disks attached to a BMS.

read

instance*

bms:servers:get

bms:servers:create

Grants permission to create BMSs.

write

-

-

bms:servers:showBaremetalServer

Grants permission to query details about a BMS.

read

instance*

bms:servers:get

bms:servers:attachVolume

Grants permission to attach EVS disks to a BMS.

write

instance*

-

bms:servers:detachVolume

Grants permission to detach EVS disks from a BMS.

write

instance*

-

bms:servers:updateMetadata

Grants permission to update BMS metadata.

write

instance*

-

bms:servers:reInstallOS

Grants permission to reinstall a BMS OS.

write

instance*

-

bms:servers:showBaremetalServerTags

Grants permission to query BMS tags.

read

instance*

bms:servers:get

bms:servers:start

Grants permission to start BMSs in a batch.

write

instance*

-

bms:servers:reboot

Grants permission to restart BMSs in a batch.

write

instance*

-

bms:servers:stop

Grants permission to stop BMSs in a batch.

write

instance*

-

bms:servers:list

Grants permission to query BMS details.

list

-

g:EnterpriseProjectId

-

bms:serverFlavors:get

Grants permission to query flavor details and extended flavor information.

list

-

-

-

bms:serverQuotas:get

Grants permission to query tenant quotas.

read

-

-

-

bms:servers:batchCreateBaremetalServerTags

Grants permission to add tags in a batch.

write

instance*

bms:servers:put

bms:servers:batchDeleteBaremetalServerTags

Grants permission to delete tags in a batch.

write

instance*

bms:servers:put

bms:servers:addNics

Grants permission to bind NICs to a BMS.

write

instance*

-

bms:server:deleteNics

Grants permission to unbind NICs from a BMS.

write

instance*

-

bms:servers:serialConsole

Grants permission to obtain an address for remotely logging in to a BMS.

read

instance*

-

bms:server:updateInterface

Grants permission to modify BMS NICs.

write

instance*

-

Each API of BMS usually supports one or more actions. Table 2 lists the supported actions and dependencies.

Table 2 Actions and dependencies supported by BMS APIs

API

Action

Dependencies

PUT /v1/{project_id}/baremetalservers/{server_id}

bms:servers:updateBaremetalServer

-

GET /v1/{project_id}/baremetalservers/{server_id}/os-interface

bms:servers:showBaremetalServerInterfaceAttachments

-

PUT /v1/{project_id}/baremetalservers/{server_id}/os-reset-password

bms:servers:resetServerPwd

-

GET /v1/{project_id}/baremetalservers/{server_id}/os-resetpwd-flag

bms:servers:showResetPasswordFlag

-

GET /v1/{project_id}/baremetalservers/{server_id}/os-server-password

bms:servers:showWindowsBaremetalServerPwd

-

DELETE /v1/{project_id}/baremetalservers/{server_id}/os-server-password

bms:servers:deletePassword

-

GET /v1/{project_id}/baremetalservers/{server_id}/os-volume_attachments

bms:servers:showBaremetalServerVolumeInfo

-

POST /v1/{project_id}/baremetalservers

bms:servers:create

-

GET /v1/{project_id}/baremetalservers/{server_id}

bms:servers:showBaremetalServer

-

POST /v1/{project_id}/baremetalservers/{server_id}/attachvolume

bms:servers:attachVolume

evs:volumes:use

DELETE /v1/{project_id}/baremetalservers/{server_id}/detachvolume/{attachment_id}

bms:servers:detachVolume

-

POST /v1/{project_id}/baremetalservers/{server_id}/metadata

bms:servers:updateMetadata

-

POST /v1/{project_id}/baremetalservers/{server_id}/reinstallos

bms:servers:reInstallOS

-

GET /v1/{project_id}/baremetalservers/{server_id}/tags

bms:servers:showBaremetalServerTags

-

POST /v1/{project_id}/baremetalservers/action

bms:servers:start

-

POST /v1/{project_id}/baremetalservers/action

bms:servers:reboot

-

POST /v1/{project_id}/baremetalservers/action

bms:servers:stop

-

GET /v1/{project_id}/baremetalservers/detail

bms:servers:list

-

GET /v1/{project_id}/baremetalservers/flavors

bms:serverFlavors:get

-

GET /v1/{project_id}/baremetalservers/limits

bms:serverQuotas:get

-

POST /v1/{project_id}/baremetalservers/{server_id}/tags/action

bms:servers:batchCreateBaremetalServerTags

-

POST /v1/{project_id}/baremetalservers/{server_id}/tags/action

bms:servers:batchDeleteBaremetalServerTags

-

POST /v1/{project_id}/baremetalservers/{server_id}/nics

bms:servers:addNics

-

POST /v1/{project_id}/baremetalservers/{server_id}/nics/delete

bms:server:deleteNics

-

POST /v1/{project_id}/baremetalservers/{server_id}/remote_console

bms:servers:serialConsole

-

PUT /v1/{project_id}/baremetalservers/{server_id}/os-interface/{port_id}

bms:server:updateInterface

-

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can define in identity policy statements for BMS.

Table 3 Resource types supported by BMS

Resource Type

URN

instance

bms:<region>:<account-id>:instance:<server-id>

Conditions

A Condition element lets you specify conditions for when an identity policy is in effect. It contains condition keys and operators.

  • The condition key that you specify can be a global condition key or a service-specific condition key.
    • Global condition keys (with the g: prefix) apply to all actions. Cloud services do not need to provide user identity information. Instead, the system automatically obtains such information and authenticates users. For details, see Global Condition Keys.
    • Service-specific condition keys (with the abbreviation of a service name plus a colon as the prefix, for example, bms:) only apply to operations of the BMS service. For details, see Table 4.
    • The number of values associated with a condition key in the request context of an API call makes the condition key single-valued or multivalued. Single-valued condition keys have at most one value in the request context of an API call. Multivalued condition keys can have multiple values in the request context of an API call. For example, a request can originate from at most one VPC endpoint, so g:SourceVpce is a single-valued condition key. You can tag resources and include multiple tag key-value pairs in a request, so g:TagKeys is a multivalued condition key.
  • A condition operator, condition key, and a condition value together constitute a complete condition statement. An identity policy can be applied only when its request conditions are met. For supported condition operators, see Condition operators.

Service-specific condition keys supported by BMS

The following table lists the condition keys that you can define in identity policies for BMS. You can include these condition keys to specify conditions for when your identity policy is in effect.

Table 4 Service-specific condition keys supported by BMS

Service-specific Condition Key

Type

Single-valued/Multivalued

Description

bms:KmsKeyId

string

Multivalued

Filters access based on the KMS key ID specified in the request parameter.

bms:Flavorld

string

Multivalued

Filters access based on the flavor ID specified in the request parameter.

bms:VpcId

string

Multivalued

Filters access based on the VPC ID specified in the request parameter.

bms:SubnetId

string

Multivalued

Filters access based on the subnet ID specified in the request parameter.

bms:ImageId

string

Single-valued

Filters access based on the image ID specified in the request parameter.

bms:SSHKeyPairName

string

Single-valued

Filters access based on the key name specified in the request parameter.

bms:AvailabilityZone

string

Single-valued

Filters access based on the availability zone specified in the request parameter.

bms:VolumeType

string

Multivalued

Filters access based on the EVS disk type specified in the request parameter.

bms:VolumeId

string

Single-valued

Filters access based on the volume ID specified in the request parameter.