Locations

This page explains how regionality applies to Cloud Logging and lists the different geographical locations where you can store your logs 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 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 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 set to 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.

You can also create user-defined buckets for any Google Cloud project. When you create a user-defined bucket, you can specify a location region for storing its logs data. After you create the bucket, the location can't be changed, but you can create a new bucket and direct logs to that bucket using sinks. To learn how to set the region 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.

Supported regions

The following regions are supported by the Cloud Logging API:

Africa

Region name Region description Log Analytics support
africa-south1 Johannesburg Yes

Americas

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

Asia Pacific

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

Europe

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

Middle East

Region name Region description Log Analytics support
me-central1 Doha Yes
me-central2 Dammam Yes
me-west1 Tel Aviv Yes

Other

Region name Region description Log Analytics support
eu Logs stored in data centers within the European Union; no additional redundancy guarantees Yes
us Logs stored in data centers within the United States; no additional redundancy guarantees Yes
global Logs stored in any data center in the world; no additional redundancy guarantees Yes

Limitations

Following are known limitations of data regionality for Cloud Logging:

  • You can't get advisory notifications about sensitive actions when you configure your Admin Activity Logs to be located in a specific region. For more information, see Overview of Sensitive Actions notifications.

  • 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