Skip to main content

Prerequisites

Before the BuiltForProd team deploys the Baseline and hands over the repositories, your organization needs to own six things, whichever edition it runs: the top of your cloud's resource hierarchy, a domain, a GitHub organization, the people who will hold the platform roles, a handful of decisions that cannot be changed cheaply later, and the pinned tooling. On the AWS edition a team mailbox for root email aliases comes with the first. This page lists them so handover is not the first time you hear about them.

Cloud organization ownership​

AWS Enterprise Baseline​

The Baseline builds one AWS Organization: a management account plus 14 member accounts created as code. You provide the management account. Two facts about it matter:

  • The default Organizations account quota allows fewer accounts than the 14 members, so a quota increase is requested from the management account before the member accounts are created.
  • The management account is exempt from service control policies by AWS design, so access to it is limited to Platform Leads through a dedicated permission set. Keep workloads out of it.

Every member account gets a root email of the form aws+acme-core-audit@company.com: plus-addressing onto one team-owned mailbox, so no root access is lost when a person leaves. That mailbox must exist and must be owned by a team, not an individual.

Azure Enterprise Baseline​

The Baseline builds the management group mg-acme and 15 subscriptions in your Microsoft Entra tenant. You provide:

  • The tenant, and either a billing scope (an Enterprise Agreement, Microsoft Customer Agreement or Microsoft Partner Agreement account) from which the code creates the subscriptions, or the 15 subscriptions created in advance for the code to adopt.
  • Microsoft Entra ID licenses. P1 for the export of the Entra sign-in logs (enable_entra_log_export, on) and for Conditional Access; P2 for every eligible user if Privileged Identity Management is switched on (enable_pim, off; about $9 per user per month).
  • The groups, ACME_* plus ACME_BreakGlass, created by your IT and looked up by display name, or created by the code with create_groups = true. The break-glass group holds your emergency accounts.
  • A security mailbox for security_alert_email, the action group receiver and the Defender for Cloud contact.

GCP Enterprise Baseline​

The Baseline builds the folders and 15 projects under your Google Cloud organization. You provide:

  • The organization on a Cloud Identity or Google Workspace account for your domain, and a billing account whose project quota allows 15 projects.
  • 2-Step Verification enforced for the organization and the Google Cloud session length set to 12 hours, both organization settings the Baseline expects.
  • The 14 groups, acme-<role>@company.com including acme-break-glass@company.com, created by your IT, or created by the code with create_groups = true.
  • Security Command Center activated at the tier you choose; scc_tier in security.hcl records it (Standard is free; Premium from about $15,000 per year).
  • A security mailbox for security_alert_email, the notification channel and the security Essential Contact.

A domain​

Every edition creates the apex zone (company.com) plus prod., staging., dev. and sandbox. subdomain zones in the core-dns account, subscription or project, and signs the apex, prod and staging zones with DNSSEC. Your registrar delegates the apex and publishes its DS record. The private zone internal.company.com is created in core-network and needs nothing from you. The DNS service is Route 53 on AWS, Azure DNS on Azure and Cloud DNS on GCP.

A GitHub organization​

The repositories are forked into your GitHub organization (your-github-org) and customized per deployment. CI never holds a cloud key: it federates from GitHub, so the trust is between your GitHub organization and your automation account, subscription or project. That is GitHub OIDC into core-auto on AWS, federated managed identities in acme-core-auto on Azure, and Workload Identity Federation in acme-core-auto on GCP. You need:

  • GitHub Environments named dev, staging and prod on each infrastructure and code repository, with required reviewers on prod;
  • GitHub teams that match the CODEOWNERS rules (platform-leads, infra-admins, security-team; devops-leads on Azure, where it co-owns the runner image), so reviews route by blast radius;
  • for the Web App Blueprint, a GitHub App (acme-runner) installed on the GitOps repository, which is how deploy pull requests are opened without a personal token, in every edition.

People and roles​

Human access goes only through groups, and the code never creates users. The roles are the same in every edition; the group names follow each cloud's convention, ACME_PlatformLeads on AWS and Azure and acme-platform-leads@company.com on GCP:

RoleAWS and Azure groupTypical members
Platform Lead: administrator, production approvalACME_PlatformLeads1
Platform EngineerACME_PlatformEngineers2 to 3
DevOps Lead: workload stages, pipelines, incidentsACME_DevOpsLeads1
DevOps EngineerACME_DevOpsEngineers2 to 4
Web application teamsACME_LeadAppDevelopers, ACME_AppDevelopers1 to 2, 3 to 8
Data engineering teamsACME_LeadETLEngineers, ACME_ETLEngineers1, 2 to 4
AI and ML teamsACME_LeadAIEngineers, ACME_AIEngineers1, 2 to 4
Security auditors, read-only without dataACME_LeadSecurityAuditors, ACME_SecurityAuditors1, 1 to 2

On AWS the groups are assigned IAM Identity Center permission sets. On Azure and GCP an all-engineers group (ACME_AllEngineers, acme-all-engineers@company.com) gives the application, data and AI groups read access to prod, and a break-glass group holds the emergency accounts. The Team Roles workbook sizes the minimum team at ten people across these roles; the AI roles are optional.

Decisions to make before the first deployment​

DecisionAWS Enterprise BaselineAzure Enterprise BaselineGCP Enterprise Baseline
Namespace (acme)Prefixes every resource, bucket, role and groupPrefixes every resource, subscription and groupPrefixes every resource and group, and is part of every project ID
Home regionus-west-2eastus2us-west1
Address planeks_vpc_map.yaml or the compact non_eks_vpc_map.yamlvnet_map.yaml or the compact vnet_map_compact.yamlnetwork_map.yaml
EgressNAT per Availability Zone in the hubhub_egress: Azure Firewall or a NAT gateway per spoke, decided before the first blueprint applyCloud NAT per VPC
Paid switchesNetwork Firewall, Transit Gateway peering, Inspector, Macie, Shield Advanced, Client VPNFirewall SKU, DNS Private Resolver, VPN gateway, DDoS Network Protection, further Defender plans, SentinelCloud Armor Enterprise, bastions, Security Command Center Premium
Compliance evaluationSOC 2 baseline pack on; 28 further packsMicrosoft cloud security benchmark and the SOC 2 baseline on; nine built-in initiativesCIS Google Cloud Foundations detections; no packs
Permanent namesRoot email aliasesThe namespace in every subscription nameProject IDs: namespace and project_id_suffix can never change once projects exist

Every paid switch is off or on by default with its price in a comment beside it. Switching the address plan later means rebuilding the network in every edition.

Tooling​

The team that will own the repositories uses the versions the code pins, so local plans match CI:

ToolAWS Enterprise BaselineAzure Enterprise BaselineGCP Enterprise Baseline
OpenTofu1.12.61.12.61.12.6
Terragrunt1.1.61.1.61.1.6
Providersaws ~> 6.65azurerm ~> 5.7, azuread ~> 3.10, azapi ~> 2.13google, google-beta ~> 8.5
tflintv0.64.0v0.64.0v0.64.0
SOPS3.13.33.13.33.13.3
Cloud CLIAWS CLI with SSO profilesAzure CLI 2.75 or later with kubeloginGoogle Cloud CLI 540 or later with gke-gcloud-auth-plugin
Remote accessAWS VPN Client, when the Client VPN is onAzure VPN Client, when the VPN gateway is onNone: Identity-Aware Proxy through the Google Cloud CLI

Engineers also need pre-commit for the local guardrail hooks. The OpenTofu explainers for AWS, Azure and GCP introduce the engine.

What BuiltForProd does with these​

The BuiltForProd team customizes the base repositories with your namespace, domain, mailboxes, GitHub organization and identifiers (every such value is marked TODO: in the code), deploys the environment, and hands over the repositories and the documentation. The Baseline product page lists the three deployment options; the shared responsibility model states what is yours from that point on.