Context
Wombat's multi-provider Terraform coverage includes AWS alongside Azure, GCP, STACKIT, OVHcloud and Hetzner Cloud (framework v1.1.0).
AWS
Use AWS Well-Architected 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
- 94 controls with provider-specific checks
- 4 relevant pillars
- 4 starting points
What Wombat adds to the provider view.
AWS gives teams a strong opinionated framework. Wombat does not replace it. It adds a provider-neutral baseline so the same workload can be assessed consistently when it also touches Azure, GCP, STACKIT, OVHcloud or Hetzner Cloud.
The current framework control pack includes 94 controls with AWS-specific checks.
Context
Use the comparison page to see where AWS Well-Architected and Wombat overlap, and where Wombat adds sovereignty and evidence coverage.
Context
The scorecard and CI action work with the same control model you use on the other providers.
AWS quickstart
Start with a pinned AWS provider, then run the same control pack you use on the other providers.
main.tf
terraform {
required_version = ">= 1.6.0"
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 5.40"
}
}
}
provider "aws" {
region = "eu-central-1"
}
terminal
wombat check . --output jsonSet AWS credentials through the standard AWS environment variables or profile. Pin the provider version to the one approved in your platform.
Known regions in the dashboard map.
Approximate locations only. The dashboard maps 35 region codes for this provider; below are the distinct locations in that map.
Approximate region locations from the dashboard map. Not a datacenter map.
N. Virginia, USA
Ohio, USA
N. California, USA
Oregon, USA
Cape Town, South Africa
Hong Kong
Mumbai, India
Hyderabad, India
Tokyo, Japan
Seoul, South Korea
Osaka, Japan
Singapore
Sydney, Australia
Jakarta, Indonesia
Melbourne, Australia
Montreal, Canada
Calgary, Canada
Frankfurt, Germany
Zurich, Switzerland
Dublin, Ireland
London, UK
Paris, France
Stockholm, Sweden
Milan, Italy
Madrid, Spain
Bahrain
UAE
Tel Aviv, Israel
São Paulo, Brazil
US GovCloud (West)
US GovCloud (East)
US Sovereign Cloud (East)
US Sovereign Cloud (West)
EU Sovereign Cloud (Ireland)
EU Sovereign Cloud (Frankfurt)
Data and verification
Data status. The region labels for AWS are compiled from the WOMBATpass dashboard region map. The current extract is dated 31 Oct 2026. The page currently lists 35 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 AWS.
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 vulnerability handling are the first review surface.
Read the Security pillar →WAF-COST
Cost Optimization
Commitments, waste and unit economics need a consistent baseline across accounts.
Read the Cost Optimization pillar →WAF-REL
Reliability
Multi-AZ, backup 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. AWS Well-Architected
Open →Controls catalogue
Open →WOMBATpass quickstart
Open →Sovereignty hub
Open →Score the AWS 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.