Context
Wombat's multi-provider Terraform coverage includes GCP alongside AWS, Azure, STACKIT, OVHcloud and Hetzner Cloud (framework v1.1.0).
Google Cloud
Use the Google Cloud Architecture Framework as the provider-native lens, then add the cross-provider sovereignty, evidence and cost controls that a multi-cloud estate needs.
- Well-Architected, extended
- Framework control coverage
- 85 controls with provider-specific checks
- 4 relevant pillars
- 4 starting points
What Wombat adds to the provider view.
Google Cloud teams already have a strong opinionated framework. Wombat adds a provider-neutral baseline so the same workload can be assessed consistently when it also touches AWS, Azure, STACKIT, OVHcloud or Hetzner Cloud.
The current framework control pack includes 85 controls with Google Cloud-specific checks.
Context
Use the comparison page to see where the Google Cloud Architecture Framework and Wombat overlap, and where Wombat adds sovereignty and evidence coverage.
Context
The scorecard and CI action use the same control model across providers.
Google Cloud quickstart
Start with the Google provider and a European region, then run the control pack against the Terraform.
main.tf
terraform {
required_version = ">= 1.6.0"
required_providers {
google = {
source = "hashicorp/google"
version = "~> 5.0"
}
}
}
provider "google" {
project = var.project_id
region = "europe-north1"
}
terminal
wombat check . --output jsonUse Application Default Credentials or the standard GOOGLE_* environment variables. Pin the provider version to your approved version.
Known regions in the dashboard map.
Approximate locations only. The dashboard maps 43 region codes for this provider; below are the distinct locations in that map.
Approximate region locations from the dashboard map. Not a datacenter map.
Iowa, USA
South Carolina, USA
N. Virginia, USA
Tennessee, USA
Oregon, USA
Washington, USA
Arizona, USA
Nevada, USA
Quebec, Canada
Montreal, Canada
São Paulo, Brazil
Santiago, Chile
Saint-Gilles, Belgium
London, UK
Frankfurt, Germany
Eemshaven, Netherlands
Zurich, Switzerland
Milan, Italy
Paris, France
Berlin, Germany
Madrid, Spain
Helsinki, Finland
Warsaw, Poland
Lisbon, Portugal
EU Sovereign Cloud, France
US Sovereign Cloud, USA
Asia Pacific Sovereign Cloud, Singapore
Taiwan
Hong Kong
Tokyo, Japan
Osaka, Japan
Seoul, South Korea
Mumbai, India
Hyderabad, India
Singapore
Jakarta, Indonesia
Sydney, Australia
Melbourne, Australia
Tel Aviv, Israel
Dubai, UAE
Doha, Qatar
Cape Town, South Africa
Data and verification
Data status. The region labels for Google Cloud are compiled from the WOMBATpass dashboard region map. The current extract is dated 31 Oct 2026. The page currently lists 43 region codes from that map.
Verification. The data has not been cross-validated with the provider. It may be incomplete, approximate or outdated.
Intended use. The information is provided for general orientation only. It is not a guarantee of service availability, a representation of exact datacenter locations, or a statement of provider certification.
Corrections. Providers and other parties may submit corrections — including the provider name, the affected region code or control count, and a public source — to page@wombat-gov.dev or open a correction issue ↗.
Trademarks. Provider names and trademarks are the property of their respective owners. Wombat is not affiliated with, endorsed by or sponsored by these providers; the names are used solely for identification.
License. The provider data on this page is published under CC BY 4.0. It is a derived compilation from the WOMBATpass dashboard and the Wombat framework control pack. Attribution: Wombat Community. The data is provided without warranty. Data license.
Methodology. Read the data methodology →
Pillars that matter on Google Cloud.
The same control model applies across providers, so the comparison stays consistent when the estate does not.
WAF-SEC
Security
Identity, network boundaries, encryption and secure configuration are the first review surface.
Read the Security pillar →WAF-COST
Cost Optimization
Committed use, waste and unit economics need a consistent baseline across projects.
Read the Cost Optimization pillar →WAF-REL
Reliability
Zone, region and recovery decisions should be scored, not assumed.
Read the Reliability pillar →WAF-SOV
Sovereign
Region choice, key custody and exit paths matter even on a mature provider.
Read the Sovereign pillar →Control coverage by pillar.
Unique controls with provider-specific checks in the current framework control pack. A control may have multiple checks.
Snapshot of the current framework control pack; counts are not a certification. See the full coverage table →
Start here.
Use the provider-native guidance for depth, and the Wombat baseline for the cross-provider score, comparison and evidence.
Wombat vs. Google Cloud Framework
Open →Controls catalogue
Open →WOMBATpass quickstart
Open →Trust center
Open →Score the Google Cloud estate against a neutral baseline
Keep the provider-native review, then use the Wombat score to compare the same workload across providers and over time.