← All insightsBest Practices

Google Cloud best practices for teams

Nir Geier, CodeWizard · 2 January 2026 · 3 min read · Intermediate

Google Cloud rewards a little discipline. These are the practices that keep it maintainable as a team and a codebase grow.

The practices

  • Use Workload Identity Federation - no exported SA keys
  • Grant least-privilege predefined roles per service account
  • Enforce uniform bucket-level access and org policies

What good looks like

A GCS bucket with uniform access via Terraform.

hcl
resource "google_storage_bucket" "assets" {
  name                        = "acme-assets"
  location                    = "EU"
  uniform_bucket_level_access = true
  versioning { enabled = true }
}

Anti-patterns to retire

  • Service-account key files instead of Workload Identity Federation
  • Primitive roles (Owner/Editor) instead of predefined/custom roles
  • Public buckets from legacy ACLs

Want senior help putting Google Cloud to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult