Access management in Cloud Interconnect

Yandex Cloud users can only perform operations on resources in accordance with the roles assigned to them. Without assigned roles, a user cannot perform most operations.

To allow access to Cloud Interconnect resources, assign relevant roles from the list below to a Yandex account, service account, federated or local users, user group, system group, or public group. Currently, a role can be assigned for a parent resource (folder or cloud) or an organization.

Access managementAccess management

Yandex Identity and Access Management checks all operations in Yandex Cloud. If an entity does not have required permissions, IAM returns an error.

To grant permissions for a resource, assign the relevant resource roles to an entity performing operations. You can assign roles to a Yandex account, service account, local user, federated user, user group, system group, or public group. For more information, see How access management works in Yandex Cloud.

Roles for a resource can be assigned by users who have one of the following roles for that resource:

• admin
• resource-manager.admin
• organization-manager.admin
• resource-manager.clouds.owner
• organization-manager.organizations.owner

Assigning rolesAssigning roles

To assign a role for the cloud:

1. Add the appropriate user, if required.
2. In the management console, on the left, select a cloud.
3. Navigate to the Access bindings tab.
4. Click Configure access.
5. In the window that opens, select User accounts.
6. Select a user from the list or use the user search option.
7. Click Add role and select a role for the cloud.
8. Click Save.

For more information about assigning roles, see the Yandex Identity and Access Management documentation.

Resources you can assign a role forResources 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.

Roles this service hasRoles this service has

The list below shows all roles used for access control in Cloud Interconnect.

Service rolesService roles

cic.auditorcic.auditor

The cic.auditor role enables viewing info on Cloud Interconnect resources.

Users with this role can:

• View info on the points of presence.
• View info on CIC partners.
• View info on trunk links.
• View info on private connections.
• View info on public connections.
• View info on Cloud Interconnect quotas.
• View info on the relevant cloud.
• View information on the relevant folder.

cic.viewercic.viewer

The cic.viewer role enables viewing info on Cloud Interconnect resources.

Users with this role can:

• View info on the points of presence.
• View info on CIC partners.
• View info on trunk links.
• View info on private connections.
• View info on public connections.
• View info on Cloud Interconnect quotas.
• View info on the relevant cloud.
• View information on the relevant folder.

This role includes the cic.auditor permissions.

cic.editorcic.editor

The cic.editor role enables managing trunk links and private and public connections, as well as viewing info on Cloud Interconnect quotas and resources.

Users with this role can:

• View info on trunk links, as well as create, modify, and delete them.
• View info on private connections, as well as create, modify, and delete them.
• View info on public connections, as well as create, modify, and delete them.
• View info on the points of presence.
• View info on CIC partners.
• View info on Cloud Interconnect quotas.
• View info on the relevant cloud.
• View information on the relevant folder.

This role includes the cic.viewer permissions.

cic.admincic.admin

The cic.admin role enables managing Cloud Interconnect resources.

Users with this role can:

• View info on trunk links, as well as create, modify, and delete them.
• View info on private connections, as well as create, modify, and delete them.
• View info on public connections, as well as create, modify, and delete them.
• View info on the points of presence.
• View info on CIC partners.
• View info on Cloud Interconnect quotas.
• View info on the relevant cloud.
• View information on the relevant folder.

This role includes the cic.editor permissions.

cic.secretViewercic.secretViewer

The cic.secretViewer role enables getting Cloud Interconnect private and public connection secrets.

cic.secretEditorcic.secretEditor

The cic.secretEditor role enables getting and modifying Cloud Interconnect private and public connection secrets.

This role includes the cic.secretViewer permissions.

Primitive rolesPrimitive roles

Primitive roles allow users to perform actions in all Yandex Cloud services.

auditorauditor

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.

viewerviewer

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.

editoreditor

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.

adminadmin

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.