⭐ Repository → 📁 Compliance Engine → 📁 CloudAware → 📁 Google → 📁 Storage

🛡️ Google Storage Bucket is located in a less cost-effective region🟢

• Contextual name: 🛡️ Bucket is located in a less cost-effective region🟢
• ID: /ce/ca/google/storage/bucket-cost-effective-region
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: BEST_PRACTICE
• Policy Categories: COST

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Google Storage Bucket
  • 🔌 Google Storage Bucket - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies Google Storage Buckets that are provisioned in Google regions known to have higher pricing compared to nearby alternatives.

Rationale

Cloud service costs vary across regions due to differences in infrastructure expenses, energy pricing, and regional market conditions. For workloads without strict geographic or latency requirements, deploying instances in more cost-efficient regions within the same continent can deliver significant cost savings without adversely affecting performance.

Impact

Migrating workloads to different regions requires careful planning to avoid service disruptions and to ensure latency, compliance, and data sovereignty requirements continue to be met.

Audit

This policy flagged an Google Storage Bucket as INCOMPLIANT if it is running in one of the following regions identified as less cost-efficient:

Region	Recommended Alternative

... see more

Remediation

Open File

Remediation

Migrate Google Cloud Storage Buckets

The migration depends on the size of the data to transfer:

• Option 1: Use gcloud (for transfers < 1 TB)
• Option 2: Use Storage Transfer Service (for transfers ≥ 1 TB)

Determine Transfer Strategy

New bucket name:

• Applications must be updated to point to {{destination-bucket}}.
• Steps: copy data → update applications → verify → delete original bucket.

Keep bucket name:

• Use a temporary bucket {{temp-bucket}}.
• Steps: copy data → downtime → delete original bucket → create new bucket with same name → copy data from temporary bucket → delete temporary bucket → verify.

Note: Bucket names must be globally unique. When retaining the same name, create the new bucket immediately after deleting the old one.

From gcloud CLI (< 1 TB)

Use this option when your data is small enough to be handled efficiently via gcloud CLI.

Create the Destination Bucket

gcloud storage buckets create gs://{{destination-bucket}} \
  --location={{target-region}} \
  --storage-class={{storage-class}}

... [see more](remediation.md)

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Resource Optimization			23		no data