Architecture overview
The BuiltForProd Baseline comes in three editions, the AWS, Azure and GCP Enterprise Baseline, and each is the same architecture built from its cloud's own services: 14 isolation units in two groups, a hub network with two isolation domains, central security and audit, keyless identity for people and pipelines, and a pipeline that plans on every pull request and applies on merge. The blueprints of each edition deploy into the workload stages and read what the Baseline publishes.
What every edition has
- 15 isolation units with the same roles.
coreholds root, audit, security, identity, network, dns, artifacts, auto, corp, public and backup;platholds sandbox, dev, staging and prod. Every unit receives the same baseline. Read landing zones. - A hub network. Two isolation domains,
prodandnonprod, that cannot reach each other, shared services in the hub, and one address plan file. Read hub-and-spoke networking. - Central security and audit. Guardrails above every unit, detection across the organization, one alert path, and evidence in
core-auditthat the units it describes cannot alter. Read defense in depth. - Human access by groups. Production is read-only for every role except Platform Leads and DevOps Leads. Read least privilege.
- Keyless CI. GitHub Actions federates into the cloud; no key is stored anywhere.
- Plan on pull request, apply on merge, drift detection on a schedule. Read GitOps and drift.
- A published landing-zone contract that the blueprints read instead of the Baseline's state. Read landing-zone contract.
AWS Enterprise Baseline
The AWS edition is one AWS Organization with 15 accounts in two organizational units, engineered around the AWS Well-Architected Framework.
| Account | Responsibility |
|---|---|
| root | The Organization, OUs, SCPs and tag policy; the state bucket; the organization CloudTrail; delegation of security services |
| security | Delegated administrator for GuardDuty, Security Hub, Inspector, Macie, IAM Access Analyzer and Firewall Manager; remediation; alerts |
| audit | The encrypted, write-protected audit bucket and the AWS Config aggregator |
| identity | IAM Identity Center permission sets and group assignments |
| network | IPAM, the hub VPC with centralized egress, the Transit Gateway, the private DNS zone and the Client VPN endpoint |
| dns, artifacts, auto | Public Route 53 zones; ECR with immutable tags; GitHub OIDC and per-stage CI roles |
| corp, public | Reserved; baselined only |
| backup | Locked backup vaults that hold copies of the workload accounts' recovery points; a protection SCP; no VPC |
| sandbox, dev, staging, prod | Workload accounts, each with a spoke VPC attached to the Transit Gateway |
The management account sits outside both OUs, so SCPs do not apply to it; it holds the Organization, billing and state only. Spokes have no NAT of their own: private traffic leaves through the Transit Gateway to the hub, which runs one NAT Gateway per Availability Zone, and each isolation domain has its own Transit Gateway route table. Three SCPs carry the non-negotiable rules; GuardDuty, Security Hub and AWS Config conformance packs detect; EventBridge remediates public buckets; one organization CloudTrail delivers to the audit account. People sign in through IAM Identity Center to twelve permission sets; pipelines use GitHub OIDC into a CI role in core-auto, one per blueprint repository and stage, then a deployer role in the target account; Baseline plans and drift checks use a read-only role. State lives in the S3 bucket acme-use1-root-tfstate. The AWS architecture overview has the full picture.
Azure Enterprise Baseline
The Azure edition is one Microsoft Entra tenant with 15 subscriptions under three management groups, engineered around the Azure Well-Architected Framework.
| Subscription | Responsibility |
|---|---|
| root | Management groups, policies and subscriptions; the state storage account; Microsoft Entra diagnostics; compliance initiatives |
| audit | The audit Log Analytics workspace, the immutable audit storage, its customer-managed key, the KQL alerts |
| security | The security workspace and the action group, the SOPS keys, the per-stage secrets syncer identities, the DDoS protection plan when it is on |
| identity | Entra groups and Azure RBAC, Privileged Identity Management, Conditional Access |
| network | The address plan, the hub VNet, the firewall policy and Azure Firewall, the DNS Private Resolver, private DNS zones, the VPN gateway when it is on |
| dns | Public DNS zones with DNSSEC |
| artifacts | Azure Container Registry, shared storage, the Unity Catalog metastore storage |
| auto | Federated CI identities per repository and stage, the CI platform vault, the runner VNet and the Container Apps runners |
| backup | One immutable, geo-redundant Backup vault with soft delete always on and a Resource Guard; no network |
| corp, public | Reserved; baselined only |
| sandbox, dev, staging, prod | Spoke VNet, peering, routes, DNS links and the contract vault, from stacks/plat-subscription |
Every spoke routes its egress and its traffic to other stages through Azure Firewall in the hub, whose policy keeps prod and nonprod apart; a NAT gateway per spoke is the alternative mode. Azure Policy at mg-acme denies what must never happen; Microsoft Defender for Cloud plans run per subscription; the action group ag-acme-security-alerts receives activity-log, KQL and Defender alerts; and the Activity Log of every subscription lands in immutable storage in acme-core-audit. People get Azure RBAC through 13 ACME_* groups plus ACME_BreakGlass, with Owner eligible through PIM when it is switched on; pipelines use one federated managed identity per blueprint repository and stage. State lives in the storage account stacmeeus2roottfstate. The Azure architecture overview has the full picture.
GCP Enterprise Baseline
The GCP edition is one Google Cloud organization with 15 projects in three folders, engineered around the Google Cloud Architecture Framework.
| Project | Responsibility |
|---|---|
| root | The seed project: the state bucket, the organization, folders and projects, organization policies, the organization log sinks |
| audit | The central log bucket, the archive bucket, their CMEK keys, the log-based detections |
| security | The metrics scope and alert policies, Security Command Center wiring, the Pub/Sub alerts topic, the SOPS keys, the per-stage secrets syncers |
| identity | Google groups and IAM bindings, Privileged Access Manager entitlements |
| network | The Shared VPC host with the hub, prod and nonprod VPCs, firewall policies, Cloud NAT, private DNS, IAP remote access |
| dns | Public Cloud DNS zones with DNSSEC |
| artifacts | Artifact Registry |
| auto | Workload Identity Federation and the per-stage CI service accounts, the optional runners |
| corp, public | Reserved; baselined only |
| backup | The protected Backup and DR vault, alone in the top-level folder backup; changed only with a second person's approval |
| sandbox, dev, staging, prod | Project baseline, the Shared VPC service attachment, the Parameter Manager contract, the observability link |
The plat projects use subnets of their domain's VPC in the Shared VPC host; the hub peers with each domain VPC and the domains never with each other, and each VPC egresses through its own Cloud NAT. 19 organization policy constraints and an IAM deny policy hold against project Owners; Security Command Center and 13 log-based detections watch the organization; two aggregated sinks send every project's audit logs to acme-core-audit. People get IAM through 14 Google groups, with Owner only through Privileged Access Manager; pipelines use Workload Identity Federation with one CI service account per blueprint repository and stage, and impersonate the deployer of their stage's project. State lives in the Cloud Storage bucket acme-usw1-root-tfstate. The GCP architecture overview has the full picture.
The blueprints on top
Each blueprint is its own set of repositories with one CI identity per stage and a state prefix per stage in the Baseline's state store. It reads network IDs, DNS zones, the registry and identities from the landing-zone contract: SSM Parameter Store on AWS, the per-stage contract vault on Azure, Parameter Manager on GCP. The blueprints page describes each one:
- AWS: Web App, Data and ETL, Secrets.
- Azure: Web App, Data and ETL, Secrets.
- GCP: Web App, Data and ETL, Secrets.