Access management in Yandex BareMetal

Yandex Cloud users can only perform the operations on resources that are allowed by the roles assigned to them. As long as a user has no roles assigned, all operations are forbidden.

To allow access to BareMetal 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.

Which roles exist in the serviceWhich roles exist in the service

In BareMetal, you can manage access using both service and primitive roles.

Service rolesService roles

baremetal.auditorbaremetal.auditor

The baremetal.auditor role enables viewing the Yandex BareMetal resource metadata.

Users with this role can:

• View info on BareMetal servers and their configuration.
• View info on private subnets and virtual routing and forwarding (VRF) segments.
• View info on the uploaded OS images for BareMetal servers.
• View details on Yandex BareMetal quotas.
• View info on the relevant folder.

baremetal.viewerbaremetal.viewer

The baremetal.viewer role enables viewing info on the Yandex BareMetal resources.

Users with this role can:

• View info on BareMetal servers and their configuration.
• View info on private subnets and virtual routing and forwarding (VRF) segments.
• View info on the uploaded OS images for BareMetal servers.
• View details on Yandex BareMetal quotas.
• View info on the relevant folder.

This role also includes the baremetal.auditor permissions.

baremetal.operatorbaremetal.operator

The baremetal.operator role enables working on the BareMetal servers and viewing info on the Yandex BareMetal resources.

Users with this role can:

• View info on BareMetal servers and their configuration.
• Use the KVM console.
• Use IPMI to power the servers on, shut them down, and restart them.
• View info on private subnets and virtual routing and forwarding (VRF) segments.
• View info on the uploaded OS images for the servers.
• View details on Yandex BareMetal quotas.
• View info on the relevant folder.

This role also includes the baremetal.viewer permissions.

baremetal.editorbaremetal.editor

The baremetal.editor role enables managing BareMetal servers, private subnets, virtual routing and forwarding (VRF) segments, and OS server images.

Users with this role can:

• View info on BareMetal servers and their configuration.
• Start and stop renting BareMetal servers and change their settings.
• View info on private subnets, as well as create, modify, and delete them.
• View info on virtual routing and forwarding (VRF) segments, as well as create, modify, and delete them.
• View info on the uploaded OS images for BareMetal servers, as well as upload, modify, and delete such images.
• Re-install OS’s for BareMetal servers.
• Use the KVM console.
• Use IPMI to power the servers on, shut them down, and restart them.
• View details on Yandex BareMetal quotas.
• View info on the relevant folder.

This role also includes the baremetal.viewer permissions.

baremetal.adminbaremetal.admin

The baremetal.admin role enables managing BareMetal servers, private subnets, virtual routing and forwarding (VRF) segments, and OS server images.

Users with this role can:

• View info on BareMetal servers and their configuration.
• Start and stop renting BareMetal servers and change their settings.
• View info on private subnets, as well as create, modify, and delete them.
• View info on virtual routing and forwarding (VRF) segments, as well as create, modify, and delete them.
• View info on the uploaded OS images for BareMetal servers, as well as upload, modify, and delete such images.
• Re-install OS’s for BareMetal servers.
• Use the KVM console.
• Use IPMI to power the servers on, shut them down, and restart them.
• View details on Yandex BareMetal quotas.
• View info on the relevant folder.

This role also includes the baremetal.editor permissions.

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 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.

See alsoSee also

Hierarchy of Yandex Cloud resources