Access management in Resource Manager
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.
About 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 at least 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 for organizations, clouds, or folders also apply to nested resources.
Which roles exist in the service
The chart below shows which roles are available in the service and how they inherit each other's permissions. For example, the editor role includes all the permissions of viewer. You can find the description of each role under the chart.
Service roles
resource-manager.auditor
The resource-manager.auditor role enables viewing cloud and folder metadata, as well as the info on the access permissions granted to clouds and folders.
Users with this role can:
- View info on clouds and their settings, as well as on the access permissions granted to clouds.
- View info on folders and their settings, as well as on the access permissions granted to folders.
- View info on the Resource Manager quotas.
resource-manager.viewer
The resource-manager.viewer role enables viewing info on clouds and folders, as well as on the access permissions to clouds and folders.
Users with this role can:
- View info on clouds and their settings, as well as on the access permissions to clouds.
- View info on folders and their settings, as well as on the access permissions to folders.
- View info on the Resource Manager quotas.
This role also includes the resource-manager.auditor permissions.
resource-manager.editor
The resource-manager.editor role enables managing clouds and folders, as well as viewing the info on the access permissions granted to clouds and folders.
Users with this role can:
- View info on clouds, their settings, and the access permissions to such clouds, as well as create, modify, and delete clouds.
- View info on folders, their settings, and the access permissions to such folders, as well as create, modify, and delete folders.
- View info on the Resource Manager quotas.
This role also includes the resource-manager.viewer permissions.
resource-manager.admin
The resource-manager.admin role enables managing clouds and folders, as well as access to those.
Users with this role can:
- View info on granted access permissions to clouds and modify such permissions.
- View info on clouds and their settings, as well as create, modify, and delete clouds.
- View info on granted access permissions to folders and modify such permissions.
- View info on folders and their settings, as well as create, modify, and delete folders.
- View info on the Resource Manager quotas.
This role also includes the resource-manager.editor permissions.
resource-manager.clouds.member
The resource-manager.clouds.member role enables viewing info on the relevant cloud and contacting the Yandex Cloud support.
The role can only be assigned for a cloud.
Users with this role can:
- View the list of technical support requests and the info on them, as well as create and close such requests, leave comments, and attach files to them.
- View info on clouds and their settings.
resource-manager.clouds.owner
The resource-manager.clouds.owner role enables running any operations within the cloud and its child resources, as well as viewing the list of billing accounts and linking the cloud to them. This role must be assigned for a billing account. By default, the users with this role get notifications on what happens to the cloud and its folders.
This role also includes the admin and resource-manager.clouds.member permissions.
The role can only be assigned for a cloud.
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.
Currently, the auditor role is available for all Yandex Cloud services, except for:
- Yandex Data Streams
- Yandex Query
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.
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 | Methods | Required roles |
|---|---|---|
| View data | ||
| View information about any resource | get, list |
viewer for this resource |
| View information about a folder or cloud | get, list |
resource-manager.viewer for the folder or cloud |
| View metadata about a folder or cloud | get, list |
resource-manager.auditor for the folder or cloud |
| Manage resources | ||
| Create a cloud | To create your first cloud, no roles are required. You only need to authenticate (a user is automatically assigned the resource-manager.clouds.owner role in the created organization). Afterwards, the resource-manager.editor or editor role for the organization is required. |
|
| Update a cloud | update |
editor or resource-manager.editor for the cloud |
| Deleting a cloud | delete |
resource-manager.clouds.owner for a cloud |
| Create a folder in the cloud | create |
editor or resource-manager.editor for the cloud |
| Update a folder | update |
editor or resource-manager.editor for the folder |
| Delete a folder | delete |
editor or resource-manager.editor for the folder |
| Manage resource access | ||
| Invite a new user to an organization | organization-manager.admin |
|
| Make a new user the owner of the cloud | setAccessBindings, updateAccessBindings |
resource-manager.clouds.owner for the cloud |
| View roles granted for a resource | listAccessBindings |
viewer for this resource |
| View roles granted for the folder or cloud | listAccessBindings |
resource-manager.viewer for the folder or cloud |
| Assign a role and revoke a role for the folder or cloud | setAccessBindings, updateAccessBindings |
admin or resource-manager.admin for the folder or cloud |