Managing access to Managed Service for OpenSearch

In this section, you will learn about:

• Resources available for role assignment.
• Available service roles.
• Roles required for specific actions.

To use the service, log in to the management console with your Yandex account, federated account, or local account.

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.

To assign roles for resources, you need either the mdb.admin role, the managed-opensearch.admin role, or one of the following roles on that resource:

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

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.

To allow access to Managed Service for OpenSearch resources (clusters and hosts, cluster backups, and accounts), assign the user the appropriate roles for a folder, cloud, or organization containing these resources.

You can also assign a role for an individual cluster in the management console, via the CLI, or API.

Roles this service hasRoles this service has

The diagram below shows available service roles and their permission inheritance hierarchy. For example, editor inherits all viewer permissions. You can find role descriptions below the diagram.

Service rolesService roles

managed-opensearch.auditormanaged-opensearch.auditor

The managed-opensearch.auditor role enables viewing info on OpenSearch clusters, access permissions granted for them, and on quotas and resource operations for Managed Service for OpenSearch.

managed-opensearch.viewermanaged-opensearch.viewer

The managed-opensearch.viewer role enables viewing info on OpenSearch clusters, their logs, and info on quotas and resource operations for Managed Service for OpenSearch.

Users with this role can:

• View info on OpenSearch clusters and access permissions granted for them.
• View info on maintenance tasks for OpenSearch clusters.
• View OpenSearch cluster logs.
• View info on quotas for Managed Service for OpenSearch.
• View info on resource operations for Managed Service for OpenSearch.

This role includes the managed-opensearch.auditor and managed-opensearch.maintenanceTask.viewer permissions.

managed-opensearch.restorermanaged-opensearch.restorer

The managed-opensearch.restorer role enables restoring OpenSearch clusters from backups and viewing info on OpenSearch clusters, their logs, as well as info on quotas and resource operations for Managed Service for OpenSearch.

Users with this role can:

• View info on OpenSearch clusters and access permissions granted for them.
• Restore OpenSearch clusters from backups.
• View info on maintenance tasks for OpenSearch clusters.
• View OpenSearch cluster logs.
• View info on quotas for Managed Service for OpenSearch.
• View info on resource operations for Managed Service for OpenSearch.

This role includes the managed-opensearch.viewer permissions.

managed-opensearch.usermanaged-opensearch.user

The managed-opensearch.user role enables using OpenSearch clusters.

managed-opensearch.editormanaged-opensearch.editor

The managed-opensearch.editor role enables managing OpenSearch clusters.

Users with this role can:

• View info on OpenSearch clusters, as well as create, use, modify, delete, run, and stop them.
• View info on access permissions granted for OpenSearch clusters.
• Restore OpenSearch clusters from backups.
• View info on maintenance tasks for OpenSearch clusters and modify such tasks.
• View OpenSearch cluster logs.
• View info on quotas for Managed Service for OpenSearch.
• View info on resource operations for Managed Service for OpenSearch.

This role includes the managed-opensearch.viewer, managed-opensearch.user, managed-opensearch.restorer, and managed-opensearch.maintenanceTask.editor permissions.

To create OpenSearch clusters, you also need the vpc.user role.

managed-opensearch.adminmanaged-opensearch.admin

The managed-opensearch.admin role enables managing OpenSearch clusters and access to them.

Users with this role can:

• View info on access permissions granted for OpenSearch clusters and modify such permissions.
• View info on OpenSearch clusters, as well as create, use, modify, delete, run, and stop them.
• Restore OpenSearch clusters from backups.
• View info on maintenance tasks for OpenSearch clusters and modify such tasks.
• View OpenSearch cluster logs.
• View info on quotas for Managed Service for OpenSearch.
• View info on resource operations for Managed Service for OpenSearch.

This role includes the managed-opensearch.editor permissions.

To create OpenSearch clusters, you also need the vpc.user role.

managed-opensearch.maintenanceTask.viewermanaged-opensearch.maintenanceTask.viewer

The managed-opensearch.maintenanceTask.viewer role enables viewing info on OpenSearch clusters, access permissions granted for them, their maintenance tasks, and on quotas and resource operations for Managed Service for OpenSearch.

This role includes the managed-opensearch.auditor permissions.

managed-opensearch.maintenanceTask.editormanaged-opensearch.maintenanceTask.editor

The managed-opensearch.maintenanceTask.editor role enables viewing info on maintenance tasks for OpenSearch clusters and modifying such tasks, as well as viewing info on OpenSearch clusters, access permissions granted for them, and on quotas and resource operations for Managed Service for OpenSearch.

This role includes the managed-opensearch.maintenanceTask.viewer permissions.

mdb.auditormdb.auditor

The mdb.auditor role grants the minimum permissions required to view info on managed database clusters (without access to data or logs).

Users with this role can view info on managed database clusters, quotas, and resource operations.

This role includes the managed-opensearch.auditor, managed-kafka.auditor, managed-mysql.auditor, managed-sqlserver.auditor, managed-postgresql.auditor, managed-spqr.auditor, managed-greenplum.auditor, managed-clickhouse.auditor, managed-redis.auditor, and managed-mongodb.auditor permissions.

mdb.viewermdb.viewer

The mdb.viewer role grants read access to managed database clusters and cluster logs.

Users with this role can read from databases, view the logs of managed database clusters, and view info on cluster maintenance tasks, clusters, quotas, and resource operations.

This role includes the managed-opensearch.viewer, managed-kafka.viewer, managed-mysql.viewer, managed-sqlserver.viewer, managed-postgresql.viewer, managed-greenplum.viewer, managed-clickhouse.viewer, managed-redis.viewer, managed-mongodb.viewer, and dataproc.viewer permissions.

mdb.adminmdb.admin

The mdb.admin role grants full access to managed database clusters.

Users with this role can create, edit, delete, run, and stop managed database clusters, manage access to clusters, create cluster backups and restore clusters from backups, read and write to databases, view info on clusters, view and modify cluster maintenance tasks, and view cluster logs as well as info on quotas and resource operations.

This role includes the mdb.viewer, vpc.user, managed-opensearch.admin, managed-kafka.admin, managed-mysql.admin, managed-sqlserver.admin, managed-postgresql.admin, managed-spqr.admin, managed-greenplum.admin, managed-clickhouse.admin, managed-redis.admin, managed-mongodb.admin, and dataproc.admin permissions.

mdb.restorermdb.restorer

The mdb.restorer role enables restoring managed database clusters from backups and grants read access to such clusters and their logs.

Users with this role can restore managed database clusters from backups, read from databases, view cluster logs, and view info on clusters, their maintenance tasks, quotas, and resource operations.

This role includes the mdb.viewer, managed-opensearch.restorer, managed-mysql.restorer, managed-sqlserver.restorer, managed-postgresql.restorer, managed-spqr.restorer, managed-greenplum.restorer, managed-clickhouse.restorer, managed-redis.restorer, and managed-mongodb.restorer permissions.

mdb.maintenanceTask.viewermdb.maintenanceTask.viewer

The mdb.maintenanceTask.viewer role grants access to information on maintenance tasks for managed database clusters.

Users with this role can view information on managed database clusters, their maintenance tasks, and access permissions granted for them, on hosts and cluster backups, as well as on service quotas and resource operations.

This role includes the mdb.auditor, managed-clickhouse.maintenanceTask.viewer, managed-greenplum.maintenanceTask.viewer, managed-kafka.maintenanceTask.viewer, managed-mongodb.maintenanceTask.viewer, managed-mysql.maintenanceTask.viewer, managed-opensearch.maintenanceTask.viewer, managed-postgresql.maintenanceTask.viewer, managed-redis.maintenanceTask.viewer, and managed-spqr.maintenanceTask.viewer permissions.

mdb.maintenanceTask.editormdb.maintenanceTask.editor

The mdb.maintenanceTask.editor role enables managing maintenance tasks for managed database clusters.

Users with this role can view information on maintenance tasks for managed database clusters and modify such tasks, view information on managed database clusters and access permissions granted for them, on cluster hosts and backups, as well as on service quotas and resource operations.

This role includes the mdb.maintenanceTask.viewer, managed-clickhouse.maintenanceTask.editor, managed-greenplum.maintenanceTask.editor, managed-kafka.maintenanceTask.editor, managed-mongodb.maintenanceTask.editor, managed-mysql.maintenanceTask.editor, managed-opensearch.maintenanceTask.editor, managed-postgresql.maintenanceTask.editor, managed-redis.maintenanceTask.editor, and managed-spqr.maintenanceTask.editor permissions.

vpc.publicAdminvpc.publicAdmin

The vpc.publicAdmin role allows you to manage NAT gateways, public IP addresses, and external network connectivity, as well as view information on the quotas, resources, and resource operations. This role grants administrator privileges for multi-interface instances that provide connectivity between multiple networks.

Users with this role can:

• View the list of cloud networks and info on them, as well as set up external access to them.
• Manage connectivity of multiple cloud networks.
• Manage multi-interface instances that provide connectivity between multiple networks.
• View the list of subnets and info on them, as well as modify them.
• View information on NAT gateways, as well as create, modify, and delete them.
• View the list of cloud resource addresses and info on them, as well as create, update, and delete public IP addresses.
• View the list of route tables and info on them, as well as link them to subnets.
• View the list of security groups and the info on them.
• View information on the IP addresses used in subnets.
• View information on Virtual Private Cloud quotas.
• View information on resource operations for Virtual Private Cloud.
• View information on resource operations for Compute Cloud.
• View information on the relevant cloud.
• View info on the relevant folder.

This role includes the vpc.viewer permissions.

You can assign a role for a cloud or folder.

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 on primitive roles, see the Yandex Cloud role reference.

Required rolesRequired roles

As a user, you need the managed-opensearch.editor role or higher for the folder that will contain the new cluster. The managed-opensearch.viewer role only allows you to view the list of clusters.

To create a Managed Service for OpenSearch cluster, you need the vpc.user role and the managed-opensearch.editor role or higher.

You can always assign a role with more permissions, e.g., managed-opensearch.admin instead of managed-opensearch.editor.

What's nextWhat's next

• How to assign a role.
• How to revoke a role.
• Learn more about access management in Yandex Cloud.
• Learn more about role inheritance.