Help Center/ Cloud Container Engine/ API Reference (Paris Regions)/ Permissions Policies and Supported Actions
Updated on 2023-08-04 GMT+08:00

Permissions Policies and Supported Actions

This chapter describes fine-grained permissions management for your CCE resources. If your account does not need individual IAM users, you can skip the operations in this chapter.

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

You can grant users permissions by using . Roles are a type of service-based, coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

If you want to allow or deny the access to an API, fine-grained authorization is a good choice.

An account has all the permissions required to call all APIs, but IAM users must be assigned the permissions to call the required APIs. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions can call the API successfully. For example, if an IAM user wants to query ECSs using an API, the user must have been granted permissions that allow the ecs:servers:list action.

Supported Actions in IAM

IAM provides system-defined policies that can be directly used. 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:

  • Permission: a statement in a policy that allows or denies certain operations.
  • APIs: REST APIs that can be called in a custom policy.
  • Actions: added to a custom policy to control permissions for specific operations.
  • Dependent actions: actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the dependent actions.
  • IAM project/Enterprise project: An action in a custom policy can be applied to either or both of these projects. 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 Management.

The check mark (√) and cross symbol (x) respectively indicate that an action takes effect or does not take effect for the corresponding type of projects.

CCE supports the following actions that can be defined in custom policies:

Table 1 Cluster

Permission

APIs

Action

IAM Project

Enterprise Project

Listing clusters in a specified project

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

cce:cluster:list

Obtaining information about a specified cluster

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

cce:cluster:get

Creating a cluster

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

cce:cluster:create

Updating information about a specified cluster

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

cce:cluster:update

Deleting a cluster

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

cce:cluster:delete

Upgrading a cluster

POST /api/v2/projects/:projectid/clusters/:clusterid/upgrade

cce:cluster:upgrade

Waking up a cluster

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

cce:cluster:start

Hibernating a cluster

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

cce:cluster:stop

Changing the specifications of a cluster

POST /api/v2/projects/{project_id}/clusters/:clusterid/resize

cce:cluster:resize

Obtaining a cluster certificate

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

cce:cluster:get

Table 2 Node

Permission

API

Action

IAM Project

Enterprise Project

Obtaining information about all nodes in a cluster

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

cce:node:list

Obtaining information about a specified node

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

cce:node:get

Creating a node

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

cce:node:create

Updating information about a specified node

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

cce:node:update

Deleting a node

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

cce:node:delete

Table 3 Job

Permission

API

Action

IAM Project

Enterprise Project

Obtaining information about a job

GET /api/v3/projects/{project_id}/jobs/{job_id}

cce:job:get

Listing all jobs

GET /api/v2/projects/{project_id}/jobs

cce:job:list

Deleting one or all jobs

DELETE /api/v2/projects/{project_id}/jobs

DELETE /api/v2/projects/{project_id}/jobs/{job_id}

cce:job:delete

Table 4 Nodepool

Permission

API

Action

IAM Project

Enterprise Project

Obtaining information about all node pools in a specified cluster

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

cce:nodepool:list

Obtaining information about a node pool

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

cce:nodepool:get

Creating a node pool

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

cce:nodepool:create

Updating information about a node pool

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

cce:nodepool:update

Deleting a node pool

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

cce:nodepool:delete

Table 5 Chart

Permission

API

Action

IAM Project

Enterprise Project

Updating a chart

PUT /v2/charts/{id}

cce:chart:update

x

Uploading a chart

POST /v2/charts

cce:chart:upload

x

Listing all charts

GET /v2/charts

cce:chart:list

x

Obtaining chart information

GET /v2/charts/{id}

cce:chart:get

x

Deleting a chart

DELETE /v2/charts/{id}

cce:chart:delete

x

Table 6 Release

Permission

API

Action

IAM Project

Enterprise Project

Updating a release

PUT /v2/releases/{name}

cce:release:update

Listing all releases

GET /v2/releases

cce:release:list

Creating a release

POST /v2/releases

cce:release:create

Obtaining information about a release

GET /v2/releases/{name}

cce:release:get

Deleting a release

DELETE /v2/releases/{name}

cce:release:delete

Table 7 Storage

Permission

API

Action

IAM Project

Enterprise Project

Creating a PersistentVolumeClaim

POST /api/v1/namespaces/{namespace}/cloudpersistentvolumeclaims

cce:storage:create

Deleting a PersistentVolumeClaim

DELETE /api/v1/namespaces/{namespace}/cloudpersistentvolumeclaims/{name}

cce:storage:delete

Listing all volumes

GET /storage/api/v1/namespaces/{namespace}/listvolumes

cce:storage:list

Table 8 Addon

Permission

API

Action

IAM Project

Enterprise Project

Creating an add-on instance

POST /api/v3/addons

cce:addonInstance:create

Obtaining information about an add-on instance

GET /api/v3/addons/{id}?cluster_id={cluster_id}

cce:addonInstance:get

Listing all add-on instances

GET /api/v3/addons?cluster_id={cluster_id}

cce:addonInstance:list

Deleting an add-on instance

DELETE /api/v3/addons/{id}?cluster_id={cluster_id}

cce:addonInstance:delete

Updating an add-on instance

PUT /api/v3/addons/{id}

cce:addonInstance:update

Table 9 Quota

Permission

API

Action

IAM Project

Enterprise Project

Querying quota details

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

cce:quota:get