Access management

Yandex.Cloud users can only perform operations on resources that are allowed by the roles assigned to them. If the user has no roles assigned, all operations are forbidden.

To allow access to resources in the Yandex Virtual Private Cloud service, assign the required roles to the user from the list below. At this time, a role can only be assigned to a parent resource (folder or cloud), and the roles are inherited by nested resources.

Note

For more information about role inheritance, see the section Inheritance of access rights in the Resource Manager documentation.

Assigning roles

To manage cloud networks, the user must have the appropriate permissions in the cloud and folders where operations will be performed.

To grant the user permissions:

  1. Open the Access management page for the selected cloud. If necessary, switch to another cloud.

  2. Select the user to assign the role to, click image, and choose Configure roles.

  3. To add a cloud role, click image in the Roles for cloud section.

    To add a folder role, select the folder and click Assign role in the Roles in folders section.

  4. Choose a role from the list.

Roles

The list below shows all roles that are considered when verifying access rights in the VPC service.

Service roles

Service roles are roles that allow access to the resources of a particular service. When VPC resource access rights are checked, Resource Manager service roles are taken into account.

resource-manager.clouds.member

When a new user is added to the cloud, they are automatically assigned the role of cloud member: resource-manager.clouds.member.

Everyone needs this role to access the cloud resources, except the cloud owners and service accounts.

This role alone does not give you the right to perform any operations and is only used in combination with other roles, such as admin, editor, or viewer.

Important

To enable a user to work in the cloud through the management console, assign them the resource-manager.clouds.member and viewer roles for the cloud. If you assign only the cloud member role for the cloud and other roles for the nested resources, the user will only be able to perform resource operations using the API or CLI.

resource-manager.clouds.owner

Theresource-manager.clouds.owner is assigned for the cloud and makes the user the owner of the cloud. The owner can perform any operation with the cloud and its resources.

Only the cloud owner can assign users the resource-manager.clouds.owner role.

A cloud must have at least one owner. The sole owner of a cloud may not give up this role.

Primitive roles

You can assign primitive roles to any resource in any service.

viewer

A user with the viewer can view lists of cloud networks and subnets.

editor

A user with the editor can perform any operations on cloud networks and subnets: create, delete, and update them.

In addition, the editor role includes all permissions of the viewer role.

admin

A user with the admin can manage access rights to resources, for example, allow other users to create cloud networks and subnets or view information about them.

In addition, the admin role includes all permissions of the role of editor.

See also

Hierarchy of Yandex.Cloud resources