Help Center/ Content Delivery Network/ API Reference/ Permissions Policies and Supported Actions/ Introduction
Updated on 2024-05-08 GMT+08:00
View PDF
Share

Introduction

This chapter describes fine-grained permissions management for your CDN. If your HUAWEI ID does not need individual IAM users, then you may skip over this chapter.

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.

You can grant users permissions 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 the list of CDN accelerated domain names using an API, the user must have been granted permissions that allow the cdn:configuration:queryDomains action.

Supported Actions

CDN 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:

  • Permissions: Statements in a policy that allow or deny 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 Differences Between IAM Projects and Enterprise Projects.

    The check mark (√) indicates that an action takes effect. The cross mark (x) indicates that an action does not take effect.

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

  • [Example] Refreshing and Preheating, including the authorization items corresponding to all the refreshing and preheating AIs of CDN, such as querying the refreshing and preheating history, enabling the refreshing function, and enabling the preheating function.
  • [Example] Domain Name Operations, including the authorization items corresponding to the CDN domain name operation APIs, such as querying domain names, creating a domain name, disabling domain names, enabling domain names, and deleting domain names.
Parent Topic: Permissions Policies and Supported Actions