Cloud Audit Logging with Cloud Storage

This page provides supplemental information for using Cloud Audit Logging with Cloud Storage. Use Cloud Audit Logging to generate logs for API operations performed in Cloud Storage.

Logged information

Within Cloud Audit Logging, there are two types of logs:

  • Admin activity logs: Entries for operations that modify the configuration or metadata of a project, bucket, or object.

  • Data access logs: Entries for operations that modify objects or read a project, bucket, or object. There are several sub-types of data access logs:

    • ADMIN_READ: Entries for operations that read the configuration or metadata of a project, bucket, or object.

    • DATA_READ: Entries for operations that read an object.

    • DATA_WRITE: Entries for operations that create or modify an object.

The following table summarizes which Cloud Storage operations fall into each log type:

Log entry type Sub-type Operations
Admin activity
  • Creating buckets
  • Deleting buckets
  • Setting/changing IAM policies
  • Setting/changing object ACLs
  • Updating bucket metadata
Data access ADMIN_READ
  • Getting bucket metadata
  • Getting IAM policies
  • Getting object ACLs
  • Listing buckets
DATA_READ
  • Getting object data
  • Getting object metadata
  • Listing objects
  • Copying/composing objects1
DATA_WRITE
  • Creating objects
  • Deleting objects
  • Updating non-ACL object metadata
  • Copying/composing objects1

1 Copying and composing are non-atomic: they each read and write data. As a result, they generate two log entries.

Cloud Storage logs use an AuditLog object and follow the same format as other Cloud Audit Logging logs. Logs contain information such as:

  • The user who made the request, including the email address of that user.
  • The resource name on which the request was made.
  • The outcome of the request.

Log settings

Admin activity logs are recorded by default. These logs do not count towards your log ingestion quota.

Data access logs pertaining to Cloud Storage operations are not recorded by default. To learn how to enable logs for data access-type operations, see Configuring Data Access Logs. Note that unlike admin activity logs, data access logs count towards your log ingestion quota and can affect your log charges in Stackdriver.

Log access

The following users can view admin activity logs:

The following users can view data access logs:

  • Project owners.
  • Users with the Private Logs Viewer IAM role.
  • Users with the logging.privateLogEntries.list IAM permission.

See Adding IAM members to a project for instructions on granting access.

Viewing logs

You can view a summary of the audit logs for your project in the Activity Stream in the Google Cloud Platform Console. A more detailed version of the logs can found in the Logs Viewer.

For instructions on filtering logs in the Logs Viewer, see the Cloud Audit Logging guide.

Log naming

Cloud Audit Logging uses standard log names for all audit logs. Admin activity logs have the following naming structure:

projects/[PROJECT_ID]/logs/cloudaudit.googleapis.com%2Factivity

Data access logs have the following naming structure:

organizations/[ORGANIZATION_ID]/logs/cloudaudit.googleapis.com%2Fdata_access

Note that for both log types, the part of the log name following /logs/ must be URL-encoded. As a consequence, the forward-slash character, /, appears as %2F.

Send feedback about...

Cloud Storage Documentation