Why it matters
Multi-region is a common default when buckets are created, but many workloads only use their data from one region and do not need the extra redundancy.How nOps finds it
nOps reads the last 7 days of Cloud Storage billing for buckets with Standard storage in a US, EU or ASIA multi-region location, billed for at least 7 days. The saving is the storage cost times the difference in list price (about 23%), plus the bucket’s replication charges. Read and download charges are shown but not counted.Before you start
Know which region the bucket’s data is used from, and whether you need copies in more than one region.How to implement
- Pick the region where the data is used most.
- Create a new bucket in that region with the same settings (access, retention, lifecycle and labels).
- Copy the data with Storage Transfer Service.
- Point applications at the new bucket, then delete the old one once nothing uses it.
Risks and considerations
- A regional bucket gives up redundancy across regions. Confirm your availability and disaster-recovery needs allow it.
- A bucket’s location cannot be changed in place, so moving means copying to a new bucket with a new name.
- Reads from other continents become cross-region and are billed differently.