Permissions Management

CDN Permissions

By default, new IAM users do not have any 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.

CDN is a global service deployed and accessed without specifying any physical region. CDN permissions are assigned to users in the global project, and users do not need to switch regions when accessing CDN.

You can grant users permissions by using roles and policies.

• Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
• Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by CDN, see Permissions Policies and Supported Actions.

A policy is a set of permissions defined in JSON format. By default, new IAM users do not have any permissions assigned. 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 CDN based on the permissions. IAM provides system policies that define the common permissions for different services, such as administrator and read-only permissions.

CDN is a global service deployed and accessed without specifying any physical region. CDN permissions are assigned to users in the global project, and users do not need to switch regions when accessing CDN.

Table 1 lists all system-defined policies supported by CDN.

Dependencies Between CDN and Other Services

Some CDN permissions depend on the policies of other cloud services. To view or use other cloud resources on the CDN console, enable the system policy access control feature of IAM and assign dependency policies for other cloud services.

• Dependency policies are assigned based on the CDN FullAccess or CDN ReadOnlyAccess policy you configured.
  

  To grant an IAM user permissions to view or use resources of other cloud services on the CDN console, you must first grant the CDN Administrator, CDN FullAccess, or CDN ReadOnlyAccess policy to the user group to which the user belongs and then grant the dependency policies listed in Table 3.

Helpful Links

• IAM Service Overview
• Creating a User and Granting CDN Permissions
• Permissions Policies and Supported Actions