[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-11 UTC。"],[],[],null,["# Locations\n\nThis page explains how regionality applies to Cloud Logging and lists the\ndifferent geographical locations where you can store your log data.\n| **Tip:** If you want to automatically apply a particular storage region to the new `_Default` and `_Required` buckets created in your organization, then configure a [default resource location](/logging/docs/default-settings#specify-region).\n\nOverview\n--------\n\nIn Logging, [log buckets](/logging/docs/routing/overview#buckets)\nare regional resources: the infrastructure that stores, indexes, and searches\nyour logs is located in a specific geographical location. With the exception of\nlog buckets in the `global`, `eu`, or `us` regions,\nGoogle Cloud manages the infrastructure so that your applications\nare available redundantly across the zones within the region of the log bucket.\n\nYour organization might be required to store its logs data in specific regions.\nThe primary factors in selecting the region where your logs are stored include\nmeeting your organization's latency, availability, or compliance requirements.\nWhen selecting a region for logs storage, consider the locations of the other\nGoogle Cloud products and services that your application uses.\n\nKey concepts\n------------\n\nThe following key concepts apply to data regionality for Logging.\n\n### Log Router locations\n\nThe [Log Router](/logging/docs/routing/overview) processes all log entries\nwritten to the Cloud Logging API. It checks each log entry against\nexisting rules to determine which log entries to store in Logging\nbuckets and which log entries to route to supported destinations using\n[sinks](/logging/docs/routing/overview#sinks). To reliably route logs, the\nLog Router also stores the logs temporarily, which buffers against temporary\ndisruptions on any sink.\n\nThe Log Router processes logs in the region in which they are received.\n\nThe Log Router might send logs to a different region based on a sink's\ndefinition or if you've opted to share log data with another\nGoogle Cloud service such as the\n[Security Command Center Threat Detection](/security-command-center/docs/how-to-configure-event-threat-detection).\nSinks apply to logs equally and regardless of region.\n\n\n### Log bucket locations\n\n[Log buckets](/logging/docs/routing/overview#buckets) are the containers in your\nGoogle Cloud project, billing account, folder, and organization that store and\norganize your logs data.\n\nFor each Google Cloud project, billing account, folder, and organization,\nLogging automatically creates two log buckets: `_Required` and\n`_Default`, which are in the `global` location.\nYou can't change the location of existing buckets.\nHowever, your organization can create a policy\nthat sets a different default location for these buckets. For more information,\nsee\n[Configure default settings for organizations and folders](/logging/docs/default-settings).\n\nYou can also [create user-defined log buckets](/logging/docs/buckets) for any\nGoogle Cloud project. When you create a user-defined log bucket, you can\nspecify the location of the log bucket. After you create the log bucket, the\nlocation can't be changed, but you can create a new bucket and then direct\nlog entries to the new log bucket by using sinks. To learn how to set the\nlocation for your buckets, see\n[Regionalize your logs](/logging/docs/regionalized-logs).\n\nLogging supports querying logs from multiple regions together, in\nwhich case queries are processed in the same locations as the buckets being\nqueried and then aggregated in the region the query was received from to return\nthe results.\n\nThe region of a log bucket is shown on the **Logs Storage** page and on\nsome dialogs. For example, when you to the Logs Explorer page and use the\n**Refine scope** selector to list log views, region information is also\ndisplayed. For this selector, when the region is `global`, both the region and\nthe current storage location are displayed in\na format similar to `GLOBAL (US-WEST4)`.\n\nSupported regions\n-----------------\n\nThe following [regions](/docs/geography-and-regions#regions_and_zones)\nare supported by Cloud Logging:\n\n#### Global\n\n| **Note:** If you want to choose the storage location for your log data or choose where your log data is analyzed with Log Analytics, then don't create log buckets in the `global` location. Instead, either use a regional log bucket or, if you have data in a BigQuery multi-region and want to colocate your log data, then set the location of your log buckets to the appropriate [multi-region location](#eu-and-us).\n\n#### Multi-regions: EU and US\n\n| **Note:** If you have data in a [BigQuery multi-region](/bigquery/docs/locations#multi-regions) and want to colocate your log data with that other business data then set the location of your log buckets to the appropriate multi-region. Alternatively, to control the storage location for your log data or where your log data is analyzed with Log Analytics, specify that location when you create the log bucket. Don't use the `global` location.\n\n#### Africa\n\n#### Americas\n\n#### Asia Pacific\n\n#### Europe\n\n#### Middle East\n\nLimitations\n-----------\n\nFollowing are known limitations of data regionality for Cloud Logging:\n\n- 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](/advisory-notifications/docs/sensitive-actions-overview).\n\n\u003c!-- --\u003e\n\n- 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](/logging/docs/routing/managed-encryption-storage).\n\n\u003c!-- --\u003e\n\n- [Error Reporting](/error-reporting/docs) is a [global product](/about/locations#global-products) and its services are available with no dependence on location. Logs buckets with a region besides `global` are automatically excluded from Error Reporting.\n\n\u003c!-- --\u003e\n\n- Cloud Monitoring is a [global product](/about/locations#global-products), and its services are available with no dependence on location. [Log-based metrics](/logging/docs/logs-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.\n\nNext steps\n----------\n\n- Learn how to\n [configure the default location](/logging/docs/default-settings#specify-region)\n for the `_Default` and `_Required` buckets created in your organization.\n\n- Learn how to\n [regionalize your logs](/logging/docs/regionalized-logs).\n\n\u003c!-- --\u003e\n\n- [View all the Google Cloud services available in locations\n worldwide](/about/locations#region).\n\n- [Explore additional location-based concepts](/docs/geography-and-regions),\n such as zones, that apply to other Google Cloud services.\n\n- Read the following whitepapers that provide best practices for data\n governance:\n\n - [Logs data: A step by step guide for overcoming common compliance\n challenges](https://services.google.com/fh/files/misc/whitepaper_data_governance_logs_how_to.pdf)\n\n - [Data governance: Principles for securing and managing\n logs](/resources/data-governance-logs-best-practices-whitepaper)"]]
