Help Center/ Cloud Container Instance/ API Reference/ Permissions Policies and Supported Actions/ Introduction
Updated on 2024-05-31 GMT+08:00
View PDF
Share

Introduction

This topic describes fine-grained permissions management for your CCI. If your account does not need individual IAM users, you may skip this topic.

You need to add a user to one or more groups, and assign permissions policies to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on CCI based on the permissions. For more information about policy syntax and example policies, see Permissions Management.

You can grant users their permissions by using roles and policies. 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 of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user queries pods using an API, the user must have been granted permissions that allow the CCI:namespaceSubResource:Get action.

Supported Actions

CCI provides system-defined policies that can be directly used in IAM. You can also create custom policies and use them to supplement system-defined policies, implementing 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.
  • IAM or enterprise projects: Type of projects for which an action will take effect. 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. For details about the differences between IAM and enterprise projects, see What Are the Differences Between IAM and Enterprise Management?

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

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

  • Namespace management actions, including actions supported by all namespace management APIs, such as the APIs for creating, querying, modifying, and deleting namespaces.
  • Pod management actions, including actions supported by all pod management APIs, such as the API for querying pods.
  • Deployment management actions, including actions supported by all Deployment management APIs, such as the APIs for creating, querying, modifying, and deleting Deployments.
  • StatefulSet management actions, including actions supported by all StatefulSet management APIs, such as the APIs for creating, querying, modifying, and deleting StatefulSets.
  • Job management actions, including actions supported by all job management APIs, such as the APIs for creating, querying, modifying, and deleting jobs.
  • Service management actions, including actions supported by all Service management APIs, such as the APIs for creating, querying, modifying, and deleting Services.
  • Ingress management actions, including actions supported by all ingress management APIs, such as the APIs for creating, querying, modifying, and deleting ingresses.
  • Network management actions, including actions supported by all network management APIs, such as the APIs for creating, querying, modifying, and deleting networks.
  • PersistentVolumeClaim management actions, including actions supported by all PersistentVolumeClaim management APIs, such as the APIs for creating, querying, modifying, and deleting PersistentVolumeClaims.
  • ConfigMap management actions, including actions supported by all ConfigMap management APIs, such as the APIs for creating, querying, modifying, and deleting ConfigMaps.
  • Secret management actions, including actions supported by all secret management APIs, such as the APIs for creating, querying, modifying, and deleting secrets.
  • ClusterRole management actions, including actions supported by all ClusterRole management APIs, such as querying ClusterRoles.
  • RoleBinding management actions, including actions supported by all RoleBinding management APIs, such as the APIs for creating, querying, modifying, and deleting RoleBindings.