IssueTracker

What you would like to accomplish: Need the ability to configure the cloud console UI for creating a new storage bucket, such that the Location Type defaults to "Region" instead of "Multi-region". We need to be able to configure this default at the domain level, so it applies to all our projects and new projects. We have many users who create buckets. Most buckets should be stored in a single region, but some need to be in multiple regions. Most of our storage usage is related to development projects that do not require the highest availability across the largest area that Multi-region provides, nor can our projects usually justify or afford the corresponding cost. We do not want to prevent Multi-region bucket creation; we just want to add an appropriate level of friction to creating Multi-region buckets, so that we ensure that it is a conscious decision.

How this might work: Org admin would be able to set the create new bucket Location Type default value, in our case setting it to "Region".

If applicable, reasons why alternative solutions are not sufficient:

• If an org policy constraint could be set to limit bucket creation to single region, that is not sufficient since we still need the option to choose multi-region at times.
• Managing this Location Type default value at the project level is not sufficient, because we have thousands of projects, with new projects being created regularly, and cannot support the overhead of custom project-level configurations. This is why we need the configuration option to be available and applicable at the domain level where it would be both manageable and effective.
• We explored creating a custom audit process wherein we would enable GCS logging, ingest logs into BigQuery, and create a Looker visualization highlighting new Multi-region buckets for follow up. This solution is a lot of setup and reactive by days or weeks, at which time it will often be too late to modify a user's storage location type, if they have already built on top of the bucket since creation.
• We explored an alerting process wherein we would enable GCS logging and alert on bucket creation events to users who have just created Multi-region buckets to verify their intent ASAP. This solution is insufficient since it is also reactive and clunky for users who will often need to return to the cloud console to redo their bucket creation work more carefully.

Other information (workarounds you have tried, documentation consulted, etc): https://cloud.google.com/storage/docs/org-policy-constraints