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

Tip: If you want to automatically apply a particular storage region to the new_Default and_Required buckets created in your organization, thenconfigure adefault resource location.

Overview

In Logging,log bucketsare regional resources: the infrastructure that stores, indexes, and searchesyour logs is located in a specific geographical location. With the exception oflog buckets in theglobal,eu, orus regions,Google Cloud manages the infrastructure so that your applicationsare available redundantly across the zones within the region of the log bucket.

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 includemeeting your organization's latency, availability, or compliance requirements.When selecting a region for logs storage, consider the locations of the otherGoogle Cloud products and services that your application uses.

Key concepts

The following key concepts apply to data regionality for Logging.

Log Router locations

TheLog Router processes all log entrieswritten to the Cloud Logging API. It checks each log entry againstexisting rules to determine which log entries to store in Loggingbuckets and which log entries to route to supported destinations usingsinks. To reliably route logs, theLog Router also stores the logs temporarily, which buffers against temporarydisruptions 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'sdefinition or if you've opted to share log data with anotherGoogle Cloud service such as theSecurity Command Center Threat Detection.Sinks apply to logs equally and regardless of region.

Log bucket locations

Log buckets are the containers in yourGoogle Cloud project, billing account, folder, and organization that store andorganize 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 theglobal location.You can't change the location of existing buckets.However, your organization can create a policythat sets a different default location for these buckets. For more information,seeConfigure default settings for organizations and folders.

You can alsocreate user-defined log buckets for anyGoogle Cloud project. When you create a user-defined log bucket, you canspecify the location of the log bucket. After you create the log bucket, thelocation can't be changed, but you can create a new bucket and then directlog entries to the new log bucket by using sinks. To learn how to set thelocation for your buckets, seeRegionalize your logs.

Note: Log buckets in theglobal region or in multi-regions don't offeradded resiliencycompared to log buckets created in single regions likeus-west1.

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

The region of a log bucket is shown on theLogs Storage page and onsome dialogs. For example, when you to the Logs Explorer page and use theRefine scope selector to list log views, region information is alsodisplayed. For this selector, when the region isglobal, both the region andthe current storage location are displayed ina format similar toGLOBAL (US-WEST4).

Supported regions

The followingregionsare supported by Cloud Logging:

Global

Note: If you want to choose the storage location for your log data orchoose where your log data is analyzed with Log Analytics, then don't createlog buckets in theglobal location. Instead, either use a regional log bucketor, if you have data in a BigQuery multi-region and want tocolocate your log data, then set the location of your log buckets to theappropriatemulti-region location.

Region name	Region description
global	Logs stored in any data centers in the world. Logs might be moved to different data centers. Unlike other global resources in Google Cloud, global log buckets in Cloud Logging don't provide additional redundancy guarantees compared to a regional log bucket.

Multi-regions: EU and US

Note: If you have data in aBigQuery multi-regionand want to colocate your log data with that other business datathen set the location of your log buckets to the appropriate multi-region.Alternatively, to control the storage location for yourlog data or where your log data is analyzed with Log Analytics,specify that location when you create the log bucket.Don't use theglobal location.

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
asia-southeast3	Bangkok
australia-southeast1	Sydney
australia-southeast2	Melbourne

Europe

Region name	Region description
europe-central2	Warsaw
europe-north1	Finland
europe-north2	Stockholm
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 get advisory notifications about sensitive actions when youconfigure your Admin Activity Logs to be located in a specific region.For more information, seeOverview of Sensitive Actions notifications.

• You can't use customer-managed encryption keys (CMEK) on a log bucket whenthe log bucket is in theglobal region. For more information, seeConfigure CMEK for log buckets.

• Error Reporting is aglobal product and its services areavailable with no dependence on location. Logs buckets with a region besidesglobal are automatically excluded from Error Reporting.

• Cloud Monitoring is aglobal product,and its services are available with no dependence on location.Log-based metrics let you definerules for aggregating logs into time series by processing logs at theLog Router. The storage location of these time series is unspecified.

Next steps

• Learn how toconfigure the default locationfor the_Default and_Required buckets created in your organization.

• Learn how toregionalize your logs.

• View all the Google Cloud services available in locationsworldwide.

• Explore additional location-based concepts,such as zones, that apply to other Google Cloud services.

• Read the following whitepapers that provide best practices for datagovernance:

  • Logs data: A step by step guide for overcoming common compliancechallenges

  • Data governance: Principles for securing and managinglogs