Locations

This page explains how regionality applies to Cloud Logging and lists the different geographical locations where you can store your log data.

Overview

In Logging, log buckets are regional resources: the infrastructure that stores, indexes, and searches your logs is located in a specific geographical location. Google Cloud manages that infrastructure so that your applications are available redundantly across the zones within that region.

Your organization might be required to store its logs data in specific regions. The primary factors in selecting the region where your logs are stored include meeting your organization's latency, availability, or compliance requirements. When selecting a region for logs storage, consider the locations of the other Google Cloud products and services that your application uses.

Key concepts

The following key concepts apply to data regionality for Logging.

Log Router locations

The Log Router processes all log entries written to the Cloud Logging API. It checks each log entry against existing rules to determine which log entries to store in Logging buckets and which log entries to route to supported destinations using sinks. To reliably route logs, the Log Router also stores the logs temporarily, which buffers against temporary disruptions on any sink.

The Log Router processes logs in the region in which they are received. The Log Router might send logs to a different region based on a sink's definition or if you've opted to share log data with another Google Cloud service such as the Security Command Center Threat Detection. Sinks apply to logs equally and regardless of region.

Log bucket locations

Log buckets are the containers in your Google Cloud project, billing account, folder, and organization that store and organize your logs data.

For each Google Cloud project, billing account, folder, and organization, Logging automatically creates two log buckets: _Required and _Default, which are in the global location. You can't change the location of existing buckets. However, your organization can create a policy that sets a different default location for these buckets. For more information, see Configure default settings for organizations and folders.

You can also create user-defined log buckets for any Google Cloud project. When you create a user-defined log bucket, you can specify the location of the log bucket. After you create the log bucket, the location can't be changed, but you can create a new bucket and then direct log entries to the new log bucket by using sinks. To learn how to set the location for your buckets, see Regionalize your logs.

Logging supports querying logs from multiple regions together, in which case queries are processed in the same locations as the buckets being queried and then aggregated in the region the query was received from to return the results.

The region of a log bucket is shown on the Logs Storage page and on some dialogs. For example, when you to the Logs Explorer page and use the Refine scope selector to list log views, region information is also displayed. For this selector, when the region is global, both the region and the current storage location are displayed in a format similar to GLOBAL (US-WEST4).

Supported regions

The following regions are supported by Cloud Logging:

Global

Region name Region description
global

Logs stored in any data centers in the world. Logs might be moved to different data centers. No additional redundancy guarantees.

Multi-regions: EU and US

Region name Region description
eu

Logs stored in any data centers within the European Union. Logs might be moved to different data centers. No additional redundancy guarantees.
us

Logs stored in any data centers within the United States. Logs might be moved to different data centers. No additional redundancy guarantees.

Africa

Region name Region description
africa-south1 Johannesburg

Americas

Region name Region description
northamerica-northeast1 Montréal
northamerica-northeast2 Toronto
northamerica-south1 Mexico
southamerica-east1 São Paulo
southamerica-west1 Santiago
us-central1 Iowa
us-east1 South Carolina
us-east4 North Virginia
us-east5 Columbus
us-south1 Dallas
us-west1 Oregon
us-west2 Los Angeles
us-west3 Salt Lake City
us-west4 Las Vegas

Asia Pacific

Region name Region description
asia-east1 Taiwan
asia-east2 Hong Kong
asia-northeast1 Tokyo
asia-northeast2 Osaka
asia-northeast3 Seoul
asia-south1 Mumbai
asia-south2 Delhi
asia-southeast1 Singapore
asia-southeast2 Jakarta
australia-southeast1 Sydney
australia-southeast2 Melbourne

Europe

Region name Region description
europe-central2 Warsaw
europe-north1 Finland
europe-southwest1 Madrid
europe-west1 Belgium
europe-west2 London
europe-west3 Frankfurt
europe-west4 Netherlands
europe-west6 Zurich
europe-west8 Milan
europe-west9 Paris
europe-west10 Berlin
europe-west12 Turin

Middle East

Region name Region description
me-central1 Doha
me-central2 Dammam
me-west1 Tel Aviv

Limitations

Following are known limitations of data regionality for Cloud Logging:

  • You can't use customer-managed encryption keys (CMEK) on a log bucket when the log bucket is in the global region. For more information, see Configure CMEK for log buckets.
  • Error Reporting is a global product and its services are available with no dependence on location. Logs buckets with a region besides global are automatically excluded from Error Reporting.
  • Cloud Monitoring is a global product, and its services are available with no dependence on location. Log-based metrics let you define rules for aggregating logs into time series by processing logs at the Log Router. The storage location of these time series is unspecified.

Next steps