Access management in Cloud CDN
Cloud CDN uses roles to manage access rights.
In this section, you will learn:
- Which resources you can assign a role for.
- Which roles exist in the service.
- Which roles are required for particular actions.
Access management
Yandex Identity and Access Management checks all operations in Yandex Cloud. If an entity does not have required permissions, this service returns an error.
To grant permissions for a resource, assign the appropriate resource roles to an entity performing operations, such as a Yandex account, service account, federated users, user group, system group, or public group. For more information, see How access management works in Yandex Cloud.
To assign roles for a resource, you need to have one of the following roles for that resource:
adminresource-manager.adminorganization-manager.adminresource-manager.clouds.ownerorganization-manager.organizations.owner
Which resources you can assign a role for
You can assign a role to an organization, cloud, or folder. The roles assigned to organizations, clouds, and folders also apply to their nested resources.
Which roles exist in the service
The chart below shows service’s roles and their permission inheritance. For example, editor inherits all viewer permissions. You can find role descriptions under the chart.
Service roles
cdn.viewer
The cdn.viewer role enables viewing info on the folder, origin groups, CDN resources, and Cloud CDN quotas.
cdn.editor
The cdn.editor role enables managing Cloud CDN resources, as well as viewing the info on quotas and the relevant folder.
Users with this role can:
- View information on origin groups as well as create, modify, and delete them.
- View information on CDN resources as well as create, modify, and delete them.
- Manage log export for the requests to CDN servers.
- Manage origin shielding.
- View information on Cloud CDN quotas.
- View information on the relevant folder.
This role also includes the cdn.viewer permissions.
cdn.admin
The cdn.admin role enables managing Cloud CDN resources, as well as viewing the info on quotas and the relevant folder.
Users with this role can:
- View information on origin groups as well as create, modify, and delete them.
- View information on CDN resources as well as create, modify, and delete them.
- Manage log export for the requests to CDN servers.
- Manage origin shielding.
- View information on Cloud CDN quotas.
- View information on the relevant folder.
This role also includes the cdn.editor permissions.
Moving forward, it will additionally include more features.
Primitive roles
Primitive roles allow users to perform actions in all Yandex Cloud services.
auditor
The auditor role grants a permission to read configuration and metadata of any Yandex Cloud resources without any access to data.
For instance, users with this role can:
- View info on a resource.
- View the resource metadata.
- View the list of operations with a resource.
auditor is the most secure role that does not grant any access to the service data. This role suits the users who need minimum access to the Yandex Cloud resources.
viewer
The viewer role grants the permissions to read the info on any Yandex Cloud resources.
This role also includes the auditor permissions.
Unlike auditor, the viewer role provides access to service data in read mode.
editor
The editor role provides permissions to manage any Yandex Cloud resources, except for assigning roles to other users, transferring organization ownership, removing an organization, and deleting Key Management Service encryption keys.
For instance, users with this role can create, modify, and delete resources.
This role also includes the viewer permissions.
admin
The admin role enables assigning any roles, except for resource-manager.clouds.owner and organization-manager.organizations.owner, and provides permissions to manage any Yandex Cloud resources (except for transferring organization ownership and removing an organization).
Prior to assigning the admin role for an organization, cloud, or billing account, make sure to check out the information on protecting privileged accounts.
This role also includes the editor permissions.
Instead of primitive roles, we recommend using service roles with more granular access control, allowing you to implement the least privilege principle.
For more information about primitive roles, see the Yandex Cloud role reference.
What roles do I need
The table below lists the roles required to perform a particular action. You can always assign a role offering more permissions than the one specified. For example, you can assign the editor role instead of viewer.
| Action | Required roles |
|---|---|
| View data | |
| View information about any resource | cdn.viewer for this resource |
| Manage CDN resources | |
| Create a resource | cdn.editor for the folder where the resources will be created |
| Change a resource's basic settings | cdn.editor for the folder with CDN resources |
| Disable a resource | cdn.editor for the folder with CDN resources |
| Configure resource caching | cdn.editor for the folder with CDN resources |
| Pre-fetch files to CDN servers | cdn.editor for the folder with CDN resources |
| Clear a resource cache | cdn.editor for the folder with CDN resources |
| Configure HTTP Request and Response headers | cdn.editor for the folder with CDN resources |
| Configure CORS responses to clients | cdn.editor for the folder with CDN resources |
| Configure HTTP methods | cdn.editor for the folder with CDN resources |
| Enable file compression | cdn.editor for the folder with CDN resources |
| Enable file segmentation | cdn.editor for the folder with CDN resources |
| Manage origin groups | |
| Create an origin group | cdn.editor for the folder with an origin group |
| Change an origin group | cdn.editor for the folder with an origin group |
| Connect an origin group to a resource | cdn.editor for the folder with the CDN resource |
| Delete an origin group | cdn.editor for the folder with an origin group |
| Manage paid features | |
| Origin shielding | cdn.editor for the folder with CDN resources |
| Log export | cdn.editor for the folder with CDN resources |
| Manage resource access | |
| Grant a role, revoke a role, and view roles granted for the resource | admin for the resource |