Access management in Managed Service for YDB
Yandex Cloud users can only perform operations on resources that are allowed by the roles assigned to them. As long as a user has no roles assigned, almost all operations are forbidden.
To enable access to YDB resources (databases and their users), assign the required roles from the list below to a Yandex account, service account, federated users, user group, system group, or public group. A role can be assigned for a parent resource (folder or cloud) whose roles are inherited by nested resources.
You can also grant a role to access a specific database. This will allow a user without any roles in the directory hosting the database to access the database according to the role assigned.
Roles for a resource can be assigned by users who have the ydb.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
Note
For more information about role inheritance, see Inheriting access permissions in the Yandex Resource Manager documentation.
Assigning roles
To assign a user a role:
- Add the required user if needed.
- In the management console
, select the appropriate cloud in the list on the left. - Go to the Access bindings tab.
- Click Assign bindings.
- In the Configuring access bindings window, click
Select subject. - Select a user from the list or search by user.
- Click
Add role. - Select a role in the cloud.
- Click Save.
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.
You can also assign a role for individual resources of the service. The list of such resources depends on the Yandex Cloud interfaces you use to assign roles:
- In the management console, you can only assign roles for a YDB DBMS.
- Via the YC CLI or Yandex Cloud API, you can assign roles for a DBMS and its backup.
Which roles exist in the service
The list below shows all roles considered when verifying access permissions in Managed Service for YDB.
Service roles
ydb.auditor
The ydb.auditor
role enables establishing connections to databases, viewing info on databases and access permissions granted to them, as well as on the database schema objects and backups.
Users with this role can:
- Establish database connections.
- View the list of databases and info on them, as well as on the access permissions granted to them.
- View info on database backups and the access permissions granted to them.
- View the list of database schema objects, such as tables, indexes, and folders, and info on them.
- View info on the quotas for Managed Service for YDB.
- View info on the relevant cloud and folder.
ydb.viewer
The ydb.viewer
role enables establishing connections to databases and querying them for reading, viewing info on databases and access permissions granted to them, as well as on the database schema objects and backups.
Users with this role can:
- Establish connections with databases and query them for reading.
- View the list of databases and info on them, as well as on the access permissions granted to them.
- View info on database backups and the access permissions granted to them.
- View the list of database schema objects, such as tables, indexes, and folders, and info on them.
- View info on the quotas for Managed Service for YDB.
- View info on the relevant cloud and folder.
This role also includes the ydb.auditor
permissions.
ydb.editor
The ydb.editor
role enables managing databases, schema objects, and database backups, as well as querying DBs for both reading and writing.
Users with this role can:
- View the list of databases, info on them and the access permissions granted to them, as well as create, run, stop, modify, and delete DBs.
- Establish connections with databases and query them for reading and writing.
- View info on database backups and the access permissions granted to them, as well as create and delete them and use them to restore databases.
- View the list of schema objects, such as tables, indexes, and folders, and info on those, as well as create, modify, and delete such objects.
- View info on the quotas for Managed Service for YDB.
- View info on the relevant cloud and folder.
This role also includes the ydb.viewer
permissions.
ydb.admin
The ydb.admin
role enables managing databases and access to them, as well as schema objects and database backups. It also allows you to query DBs for both reading and writing.
Users with this role can:
- View the list of databases and info on them, as well as create, run, stop, modify, and delete them.
- View info on granted access permissions to databases and modify such permissions.
- Establish connections with databases and query them for reading and writing.
- View info on database backups, as well as create and delete them and use them to restore databases.
- View info on granted access permissions to backups and modify such permissions.
- View the list of schema objects, such as tables, indexes, and folders, and info on those, as well as create, modify, and delete such objects.
- View info on the quotas for Managed Service for YDB.
- View info on the relevant cloud and folder.
This role also includes the ydb.editor
permissions.
ydb.kafkaApi.client
The ydb.kafkaApi.client
role allows you to work with ydb
over the Kafka API
Primitive roles
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.