Access management
In this section, you'll learn:
- What resources you can assign roles to.
- What roles exist in the service.
- What roles are required for particular actions.
About access management
All transactions in Yandex.Cloud are checked by the Identity and Access Management service. If a subject doesn't have the required permission, the service returns an error.
To grant permission to a resource, assign roles for this resource to the subject that will perform operations. Roles can be assigned to a Yandex account, service account, or system group. For more information, see How access management works in Yandex.Cloud.
Only users with the admin or resource-manager.clouds.owner role for a resource can assign roles for this resource.
What resources you can assign roles to
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.
To allow access to Managed Service for SQL Server service resources (DB clusters and hosts, cluster backups, databases, and their users), assign the user the appropriate roles for the folder or cloud hosting the resources.
What roles exist in the service
The diagram shows which roles are available in the service and how they inherit each other's permissions. For example, the editor role includes all viewer role permissions. A description of each role is given under the diagram.
Active roles in the service:
- Service roles:
-
resource-manager.clouds.owner: Grants you full access to the cloud and the resources in it. You can only assign this role for a cloud. -
resource-manager.clouds.member: The role needed to perform any operation in the cloud on behalf of a Yandex account. The role is assigned automatically when a user is added to the cloud. You can only assign this role for a cloud.
-
- Primitive roles:
What roles do I need
The table below lists the roles needed to perform a given action. You can always assign a role granting more permissions than the role specified. For example, you can assign editor instead of viewer.
| Action | Methods | Required roles |
|---|---|---|
| View data | ||
| View information about the cluster and related resources | get, list |
viewer for the folder hosting the cluster |
| Manage resources | ||
| Create clusters and backups in the folder | create |
editor for the folder |
| Change and delete clusters and related resources | update, delete |
editor for the folder hosting the cluster |
| Manage resource access | ||
| Add, edit, remove cluster users | create, update, delete |
editor for the folder hosting the cluster |
| Manage access to databases in the cluster | grantPermission, revokePermission |
editor for the folder hosting the cluster |
| Assign, revoke, and view roles granted for the resource or cloud | setAccessBindings, updateAccessBindings, listAccessBindings |
admin for this folder or cloud |