Access management in Monitoring
Yandex Cloud users can only perform operations on resources that are allowed by the roles assigned to them. If a user does not have any roles assigned, almost all operations are forbidden.
To allow access to Yandex Monitoring resources, assign the required roles from the list below to a Yandex account, service account, federated users, user group, system group, or public group.
Currently, a role can only be assigned for a parent resource (folder or cloud). Roles are inherited by nested resources.
Roles for a resource can be assigned by users who have at least one of the following roles for that resource:
admin
resource-manager.admin
organization-manager.admin
resource-manager.clouds.owner
organization-manager.organizations.owner
Note
For more information about role inheritance, see Inheriting access permissions in the Yandex Resource Manager documentation.
Assigning roles
To assign a user a role:
- Add the required user if needed.
- In the management console
, on the left, select a cloud. - Go to the Access bindings tab.
- Click Configure access.
- In the window that opens, select User accounts.
- Select a user from the list or search by user.
- Click
Add role and select a role for the cloud. - Click Save.
Which roles exist in the service
The list below shows all roles considered when verifying access permissions in Yandex Monitoring.
Service roles
monitoring.viewer
The monitoring.viewer
role enables downloading metrics and viewing info on metrics, dashboards, and widgets.
Users with this role can:
- View info on metrics and their labels, as well as download metrics.
- View the list of dashboards and widgets, as well as the info on those.
- View notification history.
- View details on Monitoring quotas.
- View info on the relevant folder.
monitoring.editor
The monitoring.editor
role enables managing dashboards and widgets, uploading and downloading metrics, and viewing the notification history and quota details.
Users with this role can:
- View info on metrics and their labels, as well as upload and download metrics.
- View lists of dashboards and widgets and info on them, as well as create, modify, and delete them.
- View notification history.
- View details on Monitoring quotas.
- View info on the relevant folder.
This role also includes the monitoring.viewer
permissions.
monitoring.admin
The monitoring.admin
role enables managing dashboards and widgets, uploading and downloading metrics, and viewing the notification history, info on quotas, and folder metadata.
Users with this role can:
- View info on metrics and their labels, as well as upload and download metrics.
- View lists of dashboards and widgets and info on them, as well as create, modify, and delete them.
- View notification history.
- View details on Monitoring quotas.
- View info on the relevant folder.
This role also includes the monitoring.editor
permissions.
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. This ensures more selective access control and implementation of the principle of least privilege.
For more information about primitive roles, see the Yandex Cloud role reference.