Cloud Container Instance

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.

For details about how to use these elements to create an IAM custom identity policy, see Creating a Custom Identity Policy.
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 an SCP.

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 SCP.
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 SCP 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 CCI, see Resources.
The Condition Key column includes 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 CCI, see Conditions.

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

**Table 1** Actions supported by CCI
Action	Description	Access Level	Resource Type (*: required)	Condition Key
cci:namespace:list	Grants permission to list all namespaces.	List	Namespace *	-
cci:namespace:create	Grants permission to create a namespace.	Write	Namespace *	-
cci:namespace:get	Grants permission to query a namespace.	Read	Namespace *	g:ResourceTag/<tag-key>
cci:namespace:delete	Grants permission to delete a namespace.	Write	Namespace *	g:ResourceTag/<tag-key>
cci:network:list	Grants permission to list all secrets.	List	Network *	-
cci:network:create	Grants permission to create a network.	Write	Network *	-
cci:network:get	Grants permission to query a network.	Read	Network *	-
cci:network:delete	Grants permission to delete a network.	Write	Network *	-
cci:network:update	Grants permission to update a network.	Write	Network *	-
cci:configmap:list	Grants permission to list all ConfigMaps.	List	ConfigMap *	-
cci:configmap:create	Grants permission to create a ConfigMap.	Write	ConfigMap *	-
cci:configmap:get	Grants permission to query a ConfigMap.	Read	ConfigMap *	-
cci:configmap:delete	Grants permission to delete a ConfigMap.	Write	ConfigMap *	-
cci:configmap:update	Grants permission to update a ConfigMap.	Write	ConfigMap *	-
cci:pod:list	Grants permission to list all pods.	List	Pod *	-
cci:pod:create	Grants permission to create a pod.	Write	Pod *	cci:AssociatePublicIp
cci:pod:get	Grants permission to query a pod.	Read	Pod *	-
cci:pod:delete	Grants permission to delete a pod.	Write	Pod *	-
cci:pod:update	Grants permission to update a pod.	Write	Pod *	-
cci:pod:getLog	Grants permission to query pod logs.	Read	Pod *	-
cci:pod:exec	Grants permission to run commands in a pod.	Write	Pod *	cci:ContainerName
cci:secret:list	Grants permission to list all secrets.	List	Secret *	-
cci:secret:create	Grants permission to create a secret.	Write	Secret *	-
cci:secret:get	Grants permission to query a secret.	Read	Secret *	-
cci:secret:delete	Grants permission to delete a secret.	Write	Secret *	-
cci:secret:update	Grants permission to update a secret.	Write	Secret *	-
cci:persistentvolume:list	Grants permission to list all PersistentVolumes.	List	PersistentVolume *	-
cci:persistentvolume:create	Grants permission to create a PersistentVolume.	Write	PersistentVolume *	-
cci:persistentvolume:get	Grants permission to query a PersistentVolume.	Read	PersistentVolume *	-
cci:persistentvolume:update	Grants permission to update a PersistentVolume.	Write	PersistentVolume *	-
cci:persistentvolume:delete	Grants permission to delete a PersistentVolume.	Write	PersistentVolume *	-
cci:persistentvolumeclaim:list	Grants permission to list all PersistentVolumeClaims.	List	PersistentVolumeClaim *	-
cci:persistentvolumeclaim:create	Grants permission to create a PersistentVolumeClaim.	Write	PersistentVolumeClaim *	-
cci:persistentvolumeclaim:get	Grants permission to query a PersistentVolumeClaim.	Read	PersistentVolumeClaim *	-
cci:persistentvolumeclaim:update	Grants permission to update a PersistentVolumeClaim.	Write	PersistentVolumeClaim *	-
cci:persistentvolumeclaim:delete	Grants permission to delete a PersistentVolumeClaim.	Write	PersistentVolumeClaim *	-
cci:storageclass:list	Grants permission to list all StorageClasses.	List	-	-
cci:deployment:list	Grants permission to list all Deployments.	List	Deployment *	-
cci:deployment:create	Grants permission to create a Deployment.	Write	Deployment *	cci:AssociatePublicIp
cci:deployment:get	Grants permission to query a Deployment.	Read	Deployment *	-
cci:deployment:delete	Grants permission to delete a Deployment.	Write	Deployment *	-
cci:deployment:update	Grants permission to update a Deployment.	Write	Deployment *	cci:AssociatePublicIp
cci:service:list	Grants permission to list all Services.	List	Service *	-
cci:service:create	Grants permission to create a Service.	Write	Service *	-
cci:service:get	Grants permission to query a Service.	Read	Service *	-
cci:service:delete	Grants permission to delete a Service.	Write	Service *	-
cci:service:update	Grants permission to update a Service.	Write	Service *	-
cci:horizontalpodautoscaler:list	Grants permission to list all HorizontalPodAutoscalers.	List	-	-
cci:horizontalpodautoscaler:create	Grants permission to create a HorizontalPodAutoscaler.	Write	-	-
cci:horizontalpodautoscaler:get	Grants permission to query a HorizontalPodAutoscaler.	Read	-	-
cci:horizontalpodautoscaler:delete	Grants permission to delete a HorizontalPodAutoscaler.	Write	-	-
cci:horizontalpodautoscaler:update	Grants permission to update a HorizontalPodAutoscaler.	Write	-	-
cci::updateobservabilityconfiguration	Grants permission to update ObservabilityConfiguration.	Write	-	-
cci::getobservabilityconfiguration	Grants permission to query ObservabilityConfiguration.	Read	-	-
cci:poolbinding:list	Grants permissions to list all PoolBindings.	List	-	-
cci:poolbinding:create	Grants permission to create a PoolBinding.	Write	-	-
cci:poolbinding:get	Grants permissions to query a PoolBinding.	Read	-	-
cci:poolbinding:delete	Grants permission to delete a PoolBinding	Write	-	-

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

**Table 2** Actions and dependencies supported by CCI APIs
API	Action	Dependencies
GET /apis/cci/v2/namespaces	cci:namespace:list	-
POST /apis/cci/v2/namespaces	cci:namespace:create	-
GET /apis/cci/v2/namespaces/{name}	cci:namespace:get	-
DELETE /apis/cci/v2/namespaces/{name}	cci:namespace:delete	-
GET /apis/cci/v2/namespaces/{namespace}/configmaps	cci:configmap:list	-
POST /apis/cci/v2/namespaces/{namespace}/configmaps	cci:configmap:create	-
GET /apis/cci/v2/namespaces/{namespace}/configmaps/{name}	cci:configmap:get	-
PUT /apis/cci/v2/namespaces/{namespace}/configmaps/{name}	cci:configmap:update	-
DELETE /apis/cci/v2/namespaces/{namespace}/configmaps/{name}	cci:configmap:delete	-
GET /apis/cci/v2/namespaces/{namespace}/pods	cci:pod:list	-
POST /apis/cci/v2/namespaces/{namespace}/pods	cci:pod:create	-
GET /apis/cci/v2/namespaces/{namespace}/pods/{name}	cci:pod:get	-
PUT /apis/cci/v2/namespaces/{namespace}/pods/{name}	cci:pod:update	-
DELETE /apis/cci/v2/namespaces/{namespace}/pods/{name}	cci:pod:delete	-
PATCH /apis/cci/v2/namespaces/{namespace}/pods/{name}	cci:pod:update	-
GET /apis/cci/v2/namespaces/{namespace}/secrets	cci:secret:list	-
POST /apis/cci/v2/namespaces/{namespace}/secrets	cci:secret:create	-
GET /apis/cci/v2/namespaces/{namespace}/secrets/{name}	cci:secret:get	-
PUT /apis/cci/v2/namespaces/{namespace}/secrets/{name}	cci:secret:update	-
DELETE /apis/cci/v2/namespaces/{namespace}/secrets/{name}	cci:secret:delete	-
GET /apis/yangtse/v2/namespaces/{namespace}/networks	cci:network:list	-
POST /apis/yangtse/v2/namespaces/{namespace}/networks	cci:network:create	-
GET /apis/yangtse/v2/namespaces/{namespace}/networks/{name}	cci:network:get	-
PUT /apis/yangtse/v2/namespaces/{namespace}/networks/{name}	cci:network:update	-
DELETE /apis/yangtse/v2/namespaces/{namespace}/networks/{name}	cci:network:delete	-
POST /apis/cci/v2/namespaces/{namespace}/pods/{name}/exec	cci:pod:exec	-
GET /apis/cci/v2/namespaces/{namespace}/pods/{name}/log	cci:pod:getLog	-
GET /apis/cci/v2/persistentvolumes	cci:persistentvolume:list	-
POST /apis/cci/v2/persistentvolumes	cci:persistentvolume:create	-
GET /apis/cci/v2/persistentvolumes/{name}	cci:persistentvolume:get	-
PUT /apis/cci/v2/persistentvolumes/{name}	cci:persistentvolume:update	-
DELETE /apis/cci/v2/persistentvolumes/{name}	cci:persistentvolume:delete	-
GET /apis/cci/v2/namespaces/{namespace}/persistentvolumeclaims	cci:persistentvolumeclaim:list	-
POST /apis/cci/v2/namespaces/{namespace}/persistentvolumeclaims	cci:persistentvolumeclaim:create	-
GET /apis/cci/v2/namespaces/{namespace}/persistentvolumeclaims/{name}	cci:persistentvolumeclaim:get	-
PUT /apis/cci/v2/namespaces/{namespace}/persistentvolumeclaims/{name}	cci:persistentvolumeclaim:update	-
DELETE /apis/cci/v2/namespaces/{namespace}/persistentvolumeclaims/{name}	cci:persistentvolumeclaim:delete	-
GET /apis/cci/v2/storageclasses	cci:storageclass:list	-
GET /apis/cci/v2/namespaces/{namespace}/services	cci:service:list	-
POST /apis/cci/v2/namespaces/{namespace}/services	cci:service:create	-
GET /apis/cci/v2/namespaces/{namespace}/services/{name}	cci:service:get	-
PUT /apis/cci/v2/namespaces/{namespace}/services/{name}	cci:service:update	-
DELETE /apis/cci/v2/namespaces/{namespace}/services/{name}	cci:service:delete	-
PATCH /apis/cci/v2/namespaces/{namespace}/services/{name}	cci:service:update	-
GET /apis/cci/v2/namespaces/{namespace}/deployments	cci:deployment:list	-
POST /apis/cci/v2/namespaces/{namespace}/deployments	cci:deployment:create	-
GET /apis/cci/v2/namespaces/{namespace}/deployments/{name}	cci:deployment:get	-
PUT /apis/cci/v2/namespaces/{namespace}/deployments/{name}	cci:deployment:update	-
DELETE /apis/cci/v2/namespaces/{namespace}/deployments/{name}	cci:deployment:delete	-
PATCH /apis/cci/v2/namespaces/{namespace}/deployments/{name}	cci:deployment:update	-
GET /apis/cci/v2/namespaces/{namespace}/horizontalpodautoscalers	cci:horizontalpodautoscaler:list	-
POST /apis/cci/v2/namespaces/{namespace}/horizontalpodautoscalers	cci:horizontalpodautoscaler:create	-
GET /apis/cci/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}	cci:horizontalpodautoscaler:get	-
PUT /apis/cci/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}	cci:horizontalpodautoscaler:update	-
DELETE /apis/cci/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}	cci:horizontalpodautoscaler:delete	-
PATCH /apis/cci/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}	cci:horizontalpodautoscaler:update	-
PUT /v1/observabilityconfiguration	cci::updateobservabilityconfiguration	-
GET /v1/observabilityconfiguration	cci::getobservabilityconfiguration	-
GET /apis/loadbalancer.networking.openvessel.io/v1/namespaces/{namespace}/poolbindings	cci:poolbinding:list	-
POST /apis/loadbalancer.networking.openvessel.io/v1/namespaces/{namespace}/poolbindings	cci:poolbinding:create	-
GET /apis/loadbalancer.networking.openvessel.io/v1/namespaces/{namespace}/poolbindings/{name}	cci:poolbinding:get	-
DELETE /apis/loadbalancer.networking.openvessel.io/v1/namespaces/{namespace}/poolbindings/{name}	cci:poolbinding:delete	-

If you want to disable OpenStack APIs in SCP policies, do not disable the vpc:nativeSubnets:get and vpc:subnets:get actions, or the network function of CCI will be abnormal.

Resources

A resource type indicates the resources that an SCP policy 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 CCI.

**Table 3** Resource types supported by CCI
Resource Type	URN
Deployment	cci:<region>:<account-id>:deployment:<namespace-name>/<deployment-name>
Secret	cci:<region>:<account-id>:secret:<namespace-name>/<secret-name>
Namespace	cci:<region>:<account-id>:namespace:<namespace-name>
Service	cci:<region>:<account-id>:service:<namespace-name>/<service-name>
Network	cci:<region>:<account-id>:network:<namespace-name>/<network-name>
PersistentVolume	cci:<region>:<account-id>:persistentvolume:<persistentvolume-name>
ImageSnapshot	cci:<region>:<account-id>:imagesnapshot:<imagesnapshot-name>
ConfigMap	cci:<region>:<account-id>:configmap:<namespace-name>/<configmap-name>
Pod	cci:<region>:<account-id>:pod:<namespace-name>/<pod-name>
PersistentVolumeClaim	cci:<region>:<account-id>:persistentvolumeclaim:<namespace-name>/<persistentvolumeclaim-name>

Conditions

Condition Key

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, cci:) apply only to operations of the 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.

Service-specific condition keys supported by CCI

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

**Table 4** Service-specific condition keys supported by CCI
Service-specific Condition Key	Type	Single-valued/Multivalued	Description
cci:AssociatePublicIp	Boolean	Single valued	Filters the permission to bind EIPs to pods by the value of cci:AssociatePublicIp.
cci:ContainerName	String	Single-valued	Filters the permission to run commands in pods by container name.