To ensure centralized log management and consistent access control, the global scope should be used when deploying Cloud Logging buckets. If a log bucket is global, it means that the logs could be physically located in any of the supported regions.
Using global buckets in Google Cloud Logging simplifies analysis across regions, offers scalability, and streamlines security measures. This approach optimizes resource utilization, facilitates cross-regional troubleshooting, and supports uniform log storage policies, making it an effective solution for organizations with diverse infrastructure needs.
Audit
To determine the location of your Cloud Logging buckets, perform the following operations:
Remediation / Resolution
Cloud Logging bucket region cannot be changed after creation. If you need to use the global location for your logs, you must create new log buckets in the "global" region and redirect the appropriate sinks to the new buckets. To re-create your Cloud Logging buckets, perform the following operations:
References
- Google Cloud Platform (GCP) Documentation
- Cloud Logging overview
- Configure log buckets
- Routing and storage overview
- GCP Command Line Interface (CLI) Documentation
- gcloud projects list
- gcloud logging buckets list
- gcloud logging buckets create
- gcloud logging buckets delete
Unlock the Remediation Steps
Free 30-day Trial
Automatically audit your configurations with Conformity
and gain access to our cloud security platform.
You are auditing:
Enable Global Logging
Risk Level: High