Access management in Cloud Backup

In this section, you will learn:

• Which resources you can assign a role for.
• Which roles exist in the service.

About access managementAbout access management

In Yandex Cloud, all transactions are checked in Yandex Identity and Access Management. If a subject does not have the required permission, the service returns an error.

To grant permissions for a resource, assign roles for this resource to the subject that will perform the operations. You can assign roles to 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.

Roles for a resource can be assigned by users who have the backup.admin or one of the following roles for that resource:

• admin
• resource-manager.admin
• organization-manager.admin
• resource-manager.clouds.owner
• organization-manager.organizations.owner

Which resources you can assign a role forWhich resources you can assign a role for

Using the Yandex Cloud console or the YC CLI, you can assign a role for a cloud or folder. These assigned roles will also apply to nested resources.

Which roles exist in the serviceWhich roles exist in the service

Service rolesService roles

backup.viewerbackup.viewer

The backup.viewer role allows you to view information on virtual machines connected to Cloud Backup, on backup policies and backups, as well as on the relevant cloud, folder, and quotas.

Users with this role can:

• View info on the connected backup providers.
• View info on access permissions assigned for backup policies.
• View info on backup policies and virtual machines linked to them.
• View info on the virtual machines connected to the service.
• View info on backups.
• View info on Cloud Backup quotas.
• View information on the relevant cloud.
• View info on the relevant folder and its statistics.

To assign the backup.viewer role, you need either the admin role for the cloud or the backup.admin one for the folder.

backup.editorbackup.editor

The backup.editor role allows you to manage the connection of virtual machines to Cloud Backup, manage backup policies, make backups, and restore VMs from existing backups.

Users with this role can:

• View info on connected backup providers, as well as connect providers available in Cloud Backup.
• Create, modify, and delete backup policies, as well as link, unlink, and run them on virtual machines.
• View info on access permissions assigned for backup policies.
• View info on backup policies and virtual machines linked to them.
• View info on virtual machines connected to Cloud Backup, as well as connect and disconnect VMs to and from the service.
• View info on backups, as well as delete them and use them to restore VMs.
• View info on Cloud Backup quotas.
• View information on the relevant cloud.
• View info on the relevant folder and its statistics.

This role also includes the backup.viewer permissions.

To assign the backup.editor role, you need either the admin role for the cloud or the backup.admin one for the folder.

backup.adminbackup.admin

The backup.admin role allows you to manage backup policies and access to them, manage the connection of virtual machines to Cloud Backup, make backups, and restore VMs from existing backups.

Users with this role can:

• View info on access permissions assigned for backup policies and modify such permissions.
• View info on connected backup providers, as well as connect providers available in Cloud Backup.
• Create, modify, and delete backup policies, as well as link, unlink, and run them on virtual machines.
• View info on backup policies and virtual machines linked to them.
• View info on virtual machines connected to Cloud Backup, as well as connect and disconnect VMs to and from the service.
• View info on backups, as well as delete them and use them to restore VMs.
• View info on Cloud Backup quotas.
• View information on the relevant cloud.
• View info on the relevant folder and its statistics.

This role also includes the backup.editor permissions.

To assign the backup.admin role, you need the admin role for the cloud.

Primitive rolesPrimitive roles

Primitive roles allow users to perform actions in all Yandex Cloud services.

auditorauditor

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.

viewerviewer

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.

editoreditor

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.

adminadmin

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.