Permissions Management

New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.

CBR is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified project in the specified region, the users only have permissions for CBR resources in the selected project. If you set Scope to All resources, the users have permissions for CBR resources in all region-specific projects. When accessing CBR resources, the users need to switch to the authorized region.

You can grant permissions by using roles or policies.

• Roles: A coarse-grained authorization strategy provided by IAM to assign permissions based on users' job responsibilities. Only a limited number of service-level roles are available for authorization. Cloud services depend on each other. When you grant permissions using roles, you also need to attach any existing dependent roles. Roles are not ideal for fine-grained authorization and least privilege access.
• Policies: A fine-grained authorization strategy that defines the permissions needed to perform specific operations on cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant IAM users only permissions to manage ECSs of a certain type. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by CBR, see Permissions Policies and Supported Actions.

Table 1 lists all system-defined permissions for CBR.

Table 2 lists the common operations supported by system-defined permissions of CBR.