Access management Audit Trails
In this section, you will learn:
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
In the Yandex Cloud console, you can assign a role for a cloud and folder. Roles assigned for clouds or folders also apply to the trails in them.
Which roles exist in the service
The chart below shows which roles are available in the service and how they inherit each other's permissions. For example, the editor
role includes all the permissions of viewer
. You can find the description of each role under the chart.
Service roles
audit-trails.auditor
The audit-trails.auditor
role lets you view information about trails.
audit-trails.viewer
The audit-trails.viewer
role gives you access to audit logs of the trails. Includes all access rights of the audit-trails.auditor
role.
audit-trails.editor
The audit-trails.editor
role lets you manage trails (create, update, and delete them). Includes all access rights of the audit-trails.viewer
role.
audit-trails.admin
The audit-trails.admin
role lets you manage your trails and user access to them. Includes all access rights of the audit-trails.editor
role.
audit-trails.configViewer
The audit-trails.configViewer
role lets you view information about trails. The role is deprecated, use the audit-trails.auditor
role instead.
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.
What roles do I need
The table shows actions and minimum roles required to perform them. You can always assign a role granting broader access rights than the role from the table. For example, instead of audit-trails.configViewer
, you can assign the audit-trails.editor
role.
Action | Role |
---|---|
Viewing information about a trail | audit-trails.auditor |
Collecting and viewing audit events in a trail | audit-trails.viewer |
Creating a trail | audit-trails.editor |
Editing a trail | audit-trails.editor |
Deleting a trail | audit-trails.editor |
Managing roles of other users for a trail | audit-trails.admin |
What's next
- Review the audit log structure.
- See an example of uploading audit logs to Cloud Logging.