Updated on 2024-05-11 GMT+08:00

Cloud Container Engine (CCE)

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.

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

For details about how to use these elements to create a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in a 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 a 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 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 CCE, see Resources.

  • The Condition Key column contains keys that you can specify in the Condition element of an SCP 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 CCE, see Conditions.

The following table lists the actions that you can define in SCP statements for CCE.

Table 1 Actions Supported by CCE

Action

Description

Access Level

Resource Type (*: required)

Condition Key

cce:cluster:createCluster

Grants permission to create a cluster.

write

cluster *

  • g:EnterpriseProjectId
  • g:TagKeys
  • g:RequestTag/<tag-key>

cce:cluster:delete

Grants permission to delete a cluster.

write

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:cluster:updateCluster

Grants permission to update a cluster.

write

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:cluster:upgrade

Grants permission to upgrade the version of a cluster.

write

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:cluster:start

Grants permission to wake up a hibernated cluster.

write

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:cluster:stop

Grants permission to hibernate a cluster.

write

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:cluster:list

Grants permission to view the cluster details list.

list

cluster *

-

cce:cluster:getCluster

Grants permission to view details about a specified cluster.

read

cluster *

  • g:ResourceTag/<tag-key>
  • g:EnterpriseProjectId

cce:cluster:getEndpoints

Grants permission to view the access address of a specified cluster.

read

cluster *

  • g:ResourceTag/<tag-key>
  • g:EnterpriseProjectId

cce:cluster:resize

Grants permission to modify the specifications of a cluster.

write

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:cluster:eipBinding

Grants permission to bind or unbind a public IP address to or from a cluster.

write

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:cluster:generateClientCredential

Grants permission to generate cluster client access credentials.

read

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:cluster:addTags

Grants permission to add tags to a cluster.

tagging

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

-

  • g:TagKeys
  • g:RequestTag/<tag-key>

cce:cluster:removeTags

Grants permission to delete tags from a cluster.

tagging

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

-

  • g:TagKeys
  • g:RequestTag/<tag-key>

cce:cluster:getConfigurationTemplate

Grants permission to obtain the configuration template information about a cluster.

read

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:cluster:getLogConfig

Grants permission to obtain the current log collection configurations of a cluster.

read

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:cluster:updateLogConfig

Grants permission to update the log collection configurations of a cluster.

write

cluster *

  • g:EnterpriseProjectId
  • g:ResourceTag/<tag-key>

cce:partition:create

Grants permission to access a partition.

write

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:partition:update

Grants permission to update a partition.

write

cluster *

g:EnterpriseProjectId

cce:partition:get

Grants permission to obtain details about a specified partition.

read

cluster *

g:EnterpriseProjectId

cce:partition:list

Grants permission to view the partition list in a specified cluster.

list

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:nodepool:create

Grants permission to create a node pool.

write

cluster *

  • cce:ClusterId
  • evs:Encrypted
  • g:EnterpriseProjectId

cce:nodepool:delete

Grants permission to delete a node pool.

write

cluster *

g:EnterpriseProjectId

cce:nodepool:updateNodepool

Grants permission to update a node pool.

write

cluster *

-

-

  • evs:Encrypted
  • g:EnterpriseProjectId

cce:nodepool:getNodepool

Grants permission to obtain details about a specified node pool.

read

cluster *

g:EnterpriseProjectId

cce:nodepool:list

Grants permission to view the node pool list in a specified cluster.

list

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:nodepool:getConfigurationTemplate

Grants permission to obtain node pool configuration templates.

read

cluster *

g:EnterpriseProjectId

cce:nodepool:getConfiguration

Grants permission to obtain the configurations of a node pool.

read

cluster *

g:EnterpriseProjectId

cce:nodepool:updateConfiguration

Grants permission to update the configurations of a node pool.

write

cluster *

g:EnterpriseProjectId

cce:node:createNode

Grants permission to create a node.

write

cluster *

  • cce:ClusterId
  • evs:Encrypted
  • g:EnterpriseProjectId

cce:node:delete

Grants permission to delete a node.

write

cluster *

g:EnterpriseProjectId

cce:node:update

Grants permission to update a node.

write

cluster *

g:EnterpriseProjectId

cce:node:getNode

Grants permission to obtain details about a specified node.

read

cluster *

g:EnterpriseProjectId

cce:node:list

Grants permission to view the node list in a specified cluster.

list

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:node:reset

Grants permission to reset a node.

write

cluster *

  • cce:ClusterId
  • evs:Encrypted
  • g:EnterpriseProjectId

cce:node:add

Grants permission to manage a node.

write

cluster *

  • cce:ClusterId
  • evs:Encrypted
  • g:EnterpriseProjectId

cce:node:remove

Grants permission to release a node.

write

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:node:migrate

Grants permission to migrate nodes between clusters.

write

cluster *

  • cce:nodeTransferSourceCluster
  • cce:nodeTransferTargetCluster
  • g:EnterpriseProjectId

cce:node:sync

Grants permission to synchronize infrastructure and resource status between nodes.

read

cluster *

g:EnterpriseProjectId

cce:quota:get

Grants permission to obtain resource quotas of cloud services used in a CCE cluster.

read

-

-

cce:addonInstance:create

Grants permission to create an add-on instance.

write

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:addonInstance:delete

Grants permission to delete an add-on instance.

write

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:addonInstance:update

Grants permission to update an add-on instance.

write

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:addonInstance:get

Grants permission to obtain details about a specified add-on instance.

read

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:addonInstance:list

Grants permission to view the add-on instance list in a specified cluster.

list

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:addonInstance:rollback

Grants permission to roll back a specified add-on instance.

write

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:chart:upload

Grants permission to upload an application chart.

write

-

-

cce:chart:delete

Grants permission to delete an application chart.

write

-

-

cce:chart:update

Grants permission to update an application chart.

write

-

-

cce:chart:listChart

Grants permission to view the application chart details list.

list

-

-

cce:chart:getChart

Grants permission to view details about an application chart specified by a user.

read

-

-

cce:chart:download

Grants permission to view the application charts downloaded by a user.

read

-

-

cce:chart:getQuota

Grants permission to view the application chart quota.

read

-

-

cce:release:create

Grants permission to create a release.

write

-

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:release:delete

Grants permission to delete a release.

write

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:release:update

Grants permission to update a release.

write

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:release:get

Grants permission to obtain details about a specified release.

read

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

cce:release:list

Grants permission to view the release list in a specified cluster.

list

cluster *

  • cce:ClusterId
  • g:EnterpriseProjectId

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

Table 2 Actions and dependencies supported by CCE APIs

API

Action

Dependencies

GET /api/v3/projects/{project_id}/quotas

cce:quota:get

-

POST /api/v3/projects/{project_id}/clusters

cce:cluster:createCluster

-

DELETE /api/v3/projects/{project_id}/clusters/{cluster_id}

cce:cluster:delete

-

PUT /api/v3/projects/{project_id}/clusters/{cluster_id}

cce:cluster:updateCluster

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgradeworkflows

cce:cluster:upgrade

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgradeworkflows

cce:cluster:upgrade

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgradeworkflows/{upgrade_workflow_id}

cce:cluster:upgrade

-

PATCH /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgradeworkflows/{upgrade_workflow_id}

cce:cluster:upgrade

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgrade

cce:cluster:upgrade

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgrade/retry

cce:cluster:upgrade

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgrade/tasks/{task_id}

cce:cluster:upgrade

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgrade/continue

cce:cluster:upgrade

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgrade/pause

cce:cluster:upgrade

-

GET /api/v3/clusterupgradefeaturegates

cce:cluster:upgrade

-

GET /api/v3/clusterupgradepaths

cce:cluster:upgrade

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/upgradeinfo

cce:cluster:upgrade

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/postcheck

cce:cluster:upgrade

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/precheck

cce:cluster:upgrade

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/precheck/tasks

cce:cluster:upgrade

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/precheck/tasks/{task_id}

cce:cluster:upgrade

-

GET /api/v3.1/projects/{project_id}/clusters/{cluster_id}/operation/snapshot/tasks

cce:cluster:upgrade

-

POST /api/v3.1/projects/{project_id}/clusters/{cluster_id}/operation/snapshot

cce:cluster:upgrade

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/upgrade/tasks

cce:cluster:upgrade

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/awake

cce:cluster:start

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/hibernate

cce:cluster:stop

-

GET /api/v3/projects/{project_id}/clusters

cce:cluster:list

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}

cce:cluster:getCluster

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/openapi

cce:cluster:getEndpoints

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/operation/resize

cce:cluster:resize

-

PUT /api/v3/projects/{project_id}/clusters/{cluster_id}/mastereip

cce:cluster:eipBinding

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/clustercert

cce:cluster:generateClientCredential

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/tags/create

cce:cluster:addTags

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/tags/delete

cce:cluster:removeTags

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/configuration/detail

cce:cluster:getConfigurationTemplate

-

GET /api/v3/projects/{project_id}/cluster/{cluster_id}/log-configs

cce:cluster:getLogConfig

-

PUT /api/v3/projects/{project_id}/cluster/{cluster_id}/log-configs

cce:cluster:updateLogConfig

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/partitions

cce:partition:create

-

PUT /api/v3/projects/{project_id}/clusters/{cluster_id}/partitions/{partition_name}

cce:partition:update

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/partitions/{partition_name}

cce:partition:get

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/partitions

cce:partition:list

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools

cce:nodepool:create

-

DELETE /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools/{nodepool_id}

cce:nodepool:delete

-

PUT /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools/{nodepool_id}

cce:nodepool:updateNodepool

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools/{nodepool_id}

cce:nodepool:getNodepool

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools

cce:nodepool:list

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools/{nodepool_id}/configuration/detail

cce:nodepool:getConfigurationTemplate

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools/{nodepool_id}/configuration

cce:nodepool:getConfiguration

-

PUT /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools/{nodepool_id}/configuration

cce:nodepool:updateConfiguration

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/nodes

cce:node:createNode

-

DELETE /api/v3/projects/{project_id}/clusters/{cluster_id}/nodes/{node_id}

cce:node:delete

-

PUT /api/v3/projects/{project_id}/clusters/{cluster_id}/nodes/{node_id}

cce:node:update

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/nodes/{node_id}

cce:node:getNode

-

GET /api/v3/projects/{project_id}/clusters/{cluster_id}/nodes

cce:node:list

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/nodes/reset

cce:node:reset

-

POST /api/v3/projects/{project_id}/clusters/{cluster_id}/nodes/add

cce:node:add

-

PUT /api/v3/projects/{project_id}/clusters/{cluster_id}/nodes/operation/remove

cce:node:remove

-

PUT /api/v3/projects/{project_id}/clusters/{cluster_id}/nodes/operation/migrateto/{target_cluster_id}

cce:node:migrate

-

GET /api/v2/projects/{project_id}/clusters/{cluster_id}/nodes/{node_id}/sync

cce:node:sync

-

POST /api/v3/addons

cce:addonInstance:create

-

DELETE /api/v3/addons/{id}

cce:addonInstance:delete

-

PUT /api/v3/addons/{id}

cce:addonInstance:update

-

GET /api/v3/addons/{id}

cce:addonInstance:get

-

GET /api/v3/addons

cce:addonInstance:list

-

POST /api/v3/addons/{id}/operation/rollback

cce:addonInstance:rollback

-

POST /v2/charts

cce:chart:upload

-

DELETE /v2/charts/{chart_id}

cce:chart:delete

-

PUT /v2/charts/{chart_id}

cce:chart:update

-

GET /v2/charts/{chart_id}

cce:chart:getChart

-

GET /v2/charts

cce:chart:listChart

-

GET /v2/charts/{chart_id}/archive

cce:chart:download

-

GET /v2/charts/{project_id}/quotas

cce:chart:getQuota

-

POST /cce/cam/v3/clusters/{cluster_id}/releases

cce:release:create

-

DELETE /cce/cam/v3/clusters/{cluster_id}/namespace/{namespace}/releases/{name}

cce:release:delete

-

PUT /cce/cam/v3/clusters/{cluster_id}/namespace/{namespace}/releases/{name}

cce:release:update

-

GET /cce/cam/v3/clusters/{cluster_id}/namespace/{namespace}/releases/{name}

cce:release:get

-

GET /cce/cam/v3/clusters/{cluster_id}/releases

cce:release:list

-

Resources

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

The following table lists the resource types that you can define in SCP statements for CCE.

Table 3 Resource types supported by CCE

Resource Type

URN

cluster

cce:<region>:<account-id>:cluster:<cluster-name>

Conditions

A Condition element lets you specify conditions for when an SCP 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, cce:) only apply to operations of the CCE 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 SCP can be applied only when its request conditions are met. For supported condition operators, see Condition operators.

The following table lists the condition keys that you can define in SCPs for CCE. You can include these condition keys to specify conditions for when your SCP is in effect.

Table 4 Service-specific condition keys supported by CCE

Service-specific Condition Key

Type

Single-valued/Multivalued

Description

cce:ClusterId

string

Single-valued

Obtains access permissions based on the cluster ID transferred in a request.

cce:nodeTransferSourceCluster

string

Single-valued

Obtains access permissions based on the ID of the source cluster from which a node is migrated.

cce:nodeTransferTargetCluster

string

Single-valued

Obtains access permissions based on the ID of the destination cluster to which a node is migrated.