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

Cloud Bastion Host (CBH)

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 also provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those 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 How IAM Is Different from Organizations for Access Control?.

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 identity policy 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 CBH, 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 is empty (-) for an action, the action does not support any condition keys.

    For details about the condition keys defined by CBH, 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 CBH.

Table 1 Actions supported by CBH

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

cbh::listAvailableZones

Grants permission to list AZs.

List

-

-

-

cbh::getEcsQuota

Grants permission to query ECS resource quotas.

Read

-

-

-

cbh::getQuota

Grants permission to query the quota of the bastion host.

Read

-

-

-

cbh::listSpecifications

Grants permission to list bastion host specifications.

List

-

-

-

cbh:instance:listInstances

Grants permission to list bastion hosts.

List

instance *

-

-

cbh:instance:getInstanceStatus

Grants permission to query bastion host status.

Read

instance *

-

cbh:instance:startInstance

Grants permission to start bastion host.

Write

instance *

-

cbh:instance:stopInstance

Grants permission to stop bastion host.

Write

instance *

-

cbh:instance:rebootInstance

Grants permission to reboot bastion host.

Write

instance *

-

cbh:instance:upgradeInstance

Grants permission to upgrade bastion host.

Write

instance *

-

cbh:instance:loginInstance

Grants permission to login bastion host as the IAM user.

Write

instance *

-

cbh:instance:resetInstancePassword

Grants permission to reset the password of bastion host.

Write

instance *

-

cbh:instance:resetInstanceLoginMethod

Grants permission to reset the login mode of bastion host.

Write

instance *

-

cbh:instance:deleteInstance

Grants permission to delete faulty bastion host.

Write

instance *

-

cbh:instance:alterInstance

Grants permission to alter bastion host.

Write

instance *

-

cbh:instance:createInstance

Grants permission to create bastion host.

Write

instance *

-

-

-

cbh:instance:bindInstanceEip

Grants permission to bind an EIP to bastion host.

Write

instance *

-

cbh:instance:unbindInstanceEip

Grants permission to unbind an EIP to bastion host.

Write

instance *

-

cbh:instance:updateInstanceSecurityGroup

Grants permission to update the security group of bastion host.

Write

instance *

-

cbh::operateAuthorization

Grants permission to create or cancel the authorization of cloud bastion host service.

Write

-

-

-

cbh::getAuthorization

Grants permission to query the authorization of cloud bastion host service from the tenant.

Read

-

-

-

cbh::listTags

Grants permission to list all tags.

List

-

-

-

cbh:instance:getInstanceTags

Grants permission to query the tag information of bastion host instance.

Read

instance *

-

cbh:instance:countInstancesByTag

Grants permission to count the number of instances that meet the label criteria.

List

instance *

-

-

cbh:instance:listInstancesByTag

Grants permission to filter instances by tags.

List

-

-

-

cbh:instance:operateInstanceTags

Grants permission to operate resource tags of bastion host instance.

Tagging

instance *

-

-

cbh:instance:getOmUrl

Grants permission to get O&M url.

Read

instance *

cbh:instance:getOmUrl

cbh:instance:rollbackInstance

Grants permission to rollback bastion host.

Write

instance *

cbh:instance:upgrade

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

Table 2 Actions and dependencies supported by CBH APIs

API

Action

Dependencies

GET /v2/{project_id}/cbs/available-zone

cbh::listAvailableZones

-

GET /v2/{project_id}/cbs/instance/specification

cbh::listSpecifications

-

GET /v2/{project_id}/cbs/instance/list

cbh:instance:listInstances

eps:enterpriseProjects:list

POST /v2/{project_id}/cbs/instance/start

cbh:instance:startInstance

-

POST /v2/{project_id}/cbs/instance/stop

cbh:instance:stopInstance

-

POST /v2/{project_id}/cbs/instance/upgrade

cbh:instance:upgradeInstance

-

POST /v2/{project_id}/cbs/instance/login

cbh:instance:loginInstance

-

PUT /v2/{project_id}/cbs/instance/password

cbh:instance:resetInstancePassword

-

PUT /v2/{project_id}/cbs/instance/login-method

cbh:instance:resetInstanceLoginMethod

-

DELETE /v2/{project_id}/cbs/instance

cbh:instance:deleteInstance

-

POST /v2/{project_id}/cbs/instance

cbh:instance:createInstance

  • vpc:quotas:list
  • vpc:subnets:list
  • vpc:subnets:get
  • vpc:securityGroups:list
  • ecs:cloudServerFlavors:get

PUT /v2/{project_id}/cbs/instance/{server_id}/security-groups

cbh:instance:updateInstanceSecurityGroup

vpc:ports:update

GET /v2/{project_id}/cbs/agency/authorization

cbh::getAuthorization

-

GET /v2/{project_id}/cbs/instance/tags

cbh::listTags

-

GET /v2/{project_id}/cbs/instance/{resource_id}/tags

cbh:instance:getInstanceTags

-

POST /v2/{project_id}/cbs/instance/count

cbh:instance:countInstancesByTag

-

POST /v2/{project_id}/cbs/instance/filter

cbh:instance:listInstancesByTag

-

POST /v2/{project_id}/cbs/instance/{server_id}/eip/bind

cbh:instance:bindInstanceEip

  • eip:publicIps:list
  • eip:publicIps:update

POST /v2/{project_id}/cbs/instance/{server_id}/eip/unbind

cbh:instance:unbindInstanceEip

  • eip:publicIps:update
  • eip:publicIps:list

GET /v2/{project_id}/cbs/instance/ecs-quota

cbh::getEcsQuota

ecs:cloudServerFlavors:get

GET /v2/{project_id}/cbs/instance/quota

cbh::getQuota

-

GET /v2/{project_id}/cbs/instance/{server_id}/status

cbh:instance:getInstanceStatus

-

POST /v2/{project_id}/cbs/instance/reboot

cbh:instance:rebootInstance

-

PUT /v2/{project_id}/cbs/instance

cbh:instance:alterInstance

-

POST /v2/{project_id}/cbs/agency/authorization

cbh::operateAuthorization

-

POST /v2/{project_id}/cbs/instance/{resource_id}/tags/action

cbh:instance:operateInstanceTags

-

GET /v2/{project_id}/cbs/instance/get-om-url

cbh:instance:getOmUrl

-

POST /v2/{project_id}/cbs/instance/rollback

cbh:instance:rollbackInstance

-

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

Table 3 Resource types supported by CBH

Resource Type

URN

instance

cbh:<region>:<account-id>:instance:<instance-id>

Conditions

Condition Key Overview

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, cbh) apply only to operations of the xx 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 operators.

Service-specific condition keys supported by CBH

The following table lists the condition keys that you can define in identity policies for CBH. 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 CBH

Service-specific Condition Key

Type

Single-valued/Multivalued

Description

cbh:VpcId

string

Single-valued

Filters access to control which VPC (ID) the instance can communicate with.

cbh:SubnetId

string

Single-valued

Filters access to control which CIDR (ID) the instance can communicate with.

cbh:AllowBindPublicIp

boolean

Single-valued

Filters access to control whether EIPs can be bound to the instance.