Sign in
Menu
Sign up
Docs
Govern your organization

Platform overview

The Terraform modules are one half of compliance.tf. The other half is the platform that decides which compliance posture each team, project and environment receives, and records who decided it. These pages are for the admin who runs an organization on compliance.tf and for the auditor who checks how it is run. Start with the model below, then go to the page for the job in front of you.

The platform model Architecture diagram: an organization owns projects and configs; a config publishes snapshots; a project has dev, staging and prod environments; a snapshot is bound or promoted to an environment, and the environment serves registry requests. publish bind · promote serves Organization Configauthors a posture Project Snapshotimmutable Environmentdev · staging · prod Registry requestterraform init

An organization owns everything. Inside it, configs author a compliance posture and freeze it into immutable snapshots, while projects organize workloads into three fixed environments. A binding connects one environment to one snapshot, and that binding is what the registry consults when a terraform init arrives.

Pages by task

ToRead
Set up your organization, its alias and its membersOrganizations and members
Decide who may author, approve and promoteAccess control
Give each workload its own dev, staging and prodProjects and environments
Author a posture and freeze it for reviewConfigs and snapshots
Put an approved posture into production, or grant an exceptionPromotion and gates
Set operational rules for every module, or for oneRulesets in the console
Give Terraform a credentialRegistry tokens
Find out why a terraform init received what it didHow a module request resolves
Choose or change a planPlans and entitlements
Show an auditor who changed what, and whenThe audit trail

Start from your role

  • You run the organization across many AWS accounts and teams. Set up projects and environments, keep one Baseline for every module served from your organization's own host, and assign who may approve before anyone promotes to prod.
  • You assess the controls for an audit. Read The audit trail for the record of each decision, Audit evidence for what the modules and the provider produce, and Access control for where separation of duties stands.
  • You own the compliance program. Read Promotion and gates for how a posture and its exceptions reach production, then Make the case for the governance summary to take to leadership.

On this page

Ask AI about this

Help improve this page