Access management in Cloud Logging

Cloud Logging uses roles to manage access permissions.

In this section, you will learn:

• What resources you can assign a role for.
• What roles exist in this service.

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 a role for a resource, a user should have the logging.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

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.

You can also assign roles for individual resources within the service:

Roles this service hasRoles this service has

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

Service rolesService roles

logging.viewerlogging.viewer

The logging.viewer role enables viewing info on log groups and sinks and access permissions assigned to them, as well as on the relevant cloud and folder.

Users with this role can:

• View info on log groups.
• View info on log sinks.
• View info on access permissions assigned to Cloud Logging resources.
• View info on log exports.
• View info on the relevant cloud and folder.

logging.editorlogging.editor

The logging.editor role enables viewing info on Cloud Logging resources and managing them.

Users with this role can:

• View info on log groups, as well as create, modify, delete, and use them.
• View info on log sinks, as well as create, modify, delete, and use them.
• View info on access permissions assigned to Cloud Logging resources.
• View info on log exports, run export, and create, modify, and delete exported files.
• View information on the relevant cloud and folder.

This role includes the logging.viewer permissions.

logging.readerlogging.reader

The logging.reader role enables viewing log group entries and info on the Cloud Logging resources, as well as the cloud and folder metadata.

Users with this role can:

• View log group entries.
• View info on log groups.
• View info on log sinks.
• View info on access permissions assigned to Cloud Logging resources.
• View info on log exports.
• View information on the relevant cloud and folder.

This role includes the logging.viewer permissions.

logging.writerlogging.writer

The logging.writer role enables adding entries to log groups and viewing info on the Cloud Logging resources, as well as on the relevant cloud and folder.

Users with this role can:

• Add entries to log groups.
• View info on log groups.
• View info on log sinks.
• View info on access permissions assigned to Cloud Logging resources.
• View info on log exports.
• View information on the relevant cloud and folder.

This role includes the logging.viewer permissions.

logging.adminlogging.admin

The logging.admin role enables managing your Cloud Logging resources and access to them, as well as viewing and adding entries to log groups.

Users with this role can:

• View info on access permissions assigned to Cloud Logging resources and modify such permissions.
• View info on log groups, as well as create, modify, delete, and use them.
• View info on log sinks, as well as create, modify, delete, and use them.
• View info on log exports, run export, and create, modify, and delete exported files.
• View and add entries to log groups.
• View info on Cloud Logging quotas.
• View information on the relevant cloud and folder.

This role includes the logging.editor, logging.reader, and logging.writer 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.