Access management in Cloud Logging
Cloud Logging uses roles to manage access rights.
In this section, you will learn:
About access management
In Yandex Cloud, all transactions are checked in Yandex Identity and Access Management. If a subject does not have the required permission, the service returns an error.
To grant permission for a resource, assign roles for this resource to the subject that will perform operations. Roles can be assigned to a Yandex account, a service account, federated users, a user group, or a system group. For more information, see How access management works in Yandex Cloud.
Only users with the admin
, resource-manager.clouds.owner
, or organization-manager.organizations.owner
role for a resource can assign roles for this resource.
Which resources you can assign a role for
Roles can be assigned for a cloud, folder, or custom log group. Roles assigned for a cloud or folder also apply to their log groups.
Which roles exist in the service
The list below shows all roles that are considered when verifying access rights in the Cloud Logging service.
Service roles
logging.viewer
The logging.viewer
role grants permission to list log groups and view information about them.
logging.editor
The logging.editor
role grants permission to update all settings of a log group, except the access rights.
The logging.editor
role includes all permissions granted by the logging.viewer
role.
logging.reader
The logging.reader
role grants permission to view records in a log group.
The logging.reader
role includes all permissions granted by the logging.viewer
role.
logging.writer
The logging.writer
role grants permission to add records to a log group.
The logging.writer
role includes all permissions granted by the logging.viewer
role.
logging.admin
The logging.admin
role grants all permissions to manage a log group, including permissions to assign roles for a log group to other users.
The logging.admin
role includes all permissions granted by the logging.editor
, logging.reader
, and logging.writer
roles.
Primitive roles
auditor
Grants permission to view service configuration and metadata without access to data.
viewer
Enables you to view information about resources.
editor
Allows you to manage resources, e.g., create, edit, and delete them.
admin
Allows you to manage your resources and access to them.
For more information about primitive roles, see Roles.