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 permission for a resource, assign roles for this resource to the subject that will perform operations. Roles can be assigned to a Yandex account, a service account, federated users, a user group, or a system group. For more information, see How access management works in Yandex Cloud.
Only users with the admin
, resource-manager.clouds.owner
, or organization-manager.organizations.owner
role for a resource can assign roles for this resource.
Which resources you can assign a role for
As with other services, you can assign roles for clouds, folder and service accounts. The roles assigned for clouds and 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 grants permission to view cloud or folder metadata and list cloud or folder roles. It is assigned to an organization, a cloud, or a folder.
resource-manager.viewer
The resource-manager.viewer
role grants permission to view cloud or folder information and list access rights granted to a cloud or a folder. It is assigned for an organization, a cloud, or a folder.
resource-manager.editor
The resource-manager.editor
role grants permission to create, edit, or delete clouds or folders. It is assigned for an organization, a cloud, or a folder.
resource-manager.admin
The resource-manager.admin
role grants permission to edit, delete, and manage access to clouds and folders. It is assigned for an organization, a cloud, or a folder.
resource-manager.clouds.member
The resource-manager.clouds.member
role is required for everyone except the cloud owners and service accounts to access resources in a cloud not owned by the organization.
resource-manager.clouds.owner
The resource-manager.clouds.owner
role grants full access to the cloud and its resources. The role can only be assigned for a cloud.
Primitive roles
auditor
Grants permission to view service configuration and metadata without access to data.
viewer
Enables you to view information about resources.
editor
Allows you to manage resources, e.g., create, edit, and delete them.
admin
Allows you to manage your resources and access to them.
For more information about primitive roles, see Roles.
What roles do I need
The table below lists the roles needed to perform a particular action. You can always assign a role granting more permissions than the role specified. For example, you can assign the editor
role instead of the viewer
one.
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 |
Updating a folder | update |
editor or resource-manager.editor for the folder |
Deleting a folder | delete |
editor or resource-manager.editor for the folder |
Managing resource access | ||
Inviting 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 |