Access management in Managed Service for YTsaurus
Note
The service is at the Preview stage.
In this section, you will learn:
- What resources you can assign a role for.
- What roles this service has.
- What roles are required for specific actions.
To use the service, log in to the management console with a Yandex account or federated account.
Access management
Yandex Identity and Access Management checks all operations in Yandex Cloud. If an entity does not have required permissions, this service returns an error.
To grant permissions for a resource, assign the appropriate resource roles to an entity performing operations, such as 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.
To assign a role for a resource, you should have the managed-ytsaurus.admin
role or one of the following roles for that resource:
admin
resource-manager.admin
organization-manager.admin
resource-manager.clouds.owner
organization-manager.organizations.owner
Resources you can assign a role for
You can assign a role to an organization, cloud, or folder. The roles assigned to organizations, clouds, and folders also apply to their nested resources.
To allow access to Managed Service for YTsaurus resources, such as clusters and accounts, give the user the relevant roles for the folder, cloud, or organization containing those resources.
What roles exist in this service
Below is a list of all roles relevant for access control in the service.
Service roles
managed-ytsaurus.auditor
The managed-ytsaurus.auditor
role enables viewing info on YTsaurus clusters as well as data on the quotas and resource operations for Managed Service for YTsaurus.
managed-ytsaurus.viewer
The managed-ytsaurus.viewer
role enables viewing info on YTsaurus clusters, quotas, and resource operations for Managed Service for YTsaurus.
This role includes the managed-ytsaurus.auditor
permissions.
managed-ytsaurus.user
The managed-ytsaurus.user
role enables performing basic operations on YTsaurus clusters.
Users with this role can:
- Use the YTsaurus web UI.
- View info on YTsaurus clusters.
- View info on the quotas for Managed Service for YTsaurus.
- View info on resource operations for Managed Service for YTsaurus.
This role includes the managed-ytsaurus.viewer
permissions.
managed-ytsaurus.editor
The managed-ytsaurus.editor
role enables managing YTsaurus clusters, as well as getting info on the quotas and service resource operations.
Users with this role can:
- View information on YTsaurus clusters, as well as create, modify, delete, run, and stop them.
- View info on the quotas for Managed Service for YTsaurus.
- View info on resource operations for Managed Service for YTsaurus.
- Use the YTsaurus web UI.
This role includes the managed-ytsaurus.user
permissions.
To create YTsaurus clusters, you also need the vpc.user
role.
managed-ytsaurus.admin
The managed-ytsaurus.admin
role enables managing YTsaurus clusters, as well as getting info on the quotas and service resource operations for Managed Service for YTsaurus.
Users with this role can:
- View info on YTsaurus clusters, as well as create, modify, run, stop, and delete them.
- View info on the quotas for Managed Service for YTsaurus.
- View info on resource operations for Managed Service for YTsaurus.
- Use the YTsaurus web UI.
This role includes the managed-ytsaurus.editor
permissions.
To create YTsaurus clusters, you also need the vpc.user
role.
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 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 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 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.
Roles required
To use the service, the user needs the managed-ytsaurus.editor
role or higher for the folder in which the cluster is created. With the managed-ytsaurus.viewer
role, one can only view the list of clusters.
To create an Managed Service for YTsaurus cluster, the following roles are required: vpc.user, iam.serviceAccounts.user, and managed-ytsaurus.admin
or higher.
You can always assign a role with more permissions. For example, you can assign the managed-ytsaurus.admin
role instead of managed-ytsaurus.editor
.