Whirlwind Platform Architecture
Overview
Coordinate changes that span the full Whirlwind stack across Terragrunt, Terraform infrastructure, networking DNS, and Ansible configuration.
Cross-repo workflow
- •Define the change goal and the impacted runtime surface.
- •Map the change to repos using
references/cross-repo-map.md. - •Identify required contracts (DNS-01, SSM parameters, secrets, IAM roles).
- •Sequence the changes so shared networking and infrastructure land before configuration.
- •Validate with targeted applies and one environment before scaling out.
Common change patterns
- •DNS-01 or hosted zone changes: update networking module, then Terragrunt stacks, then workloads.
- •Ansible pipeline changes: update Terraform infra CI/CD, then Ansible repo variables and scripts.
- •Compute changes (ASG or NLB): update Terraform infra modules, then Terragrunt wiring, then Ansible inventory strategy.
References
- •
references/cross-repo-map.md - •
references/dns-01-architecture.md - •
references/auto-scaling-plan.md - •
references/operational-contracts.md - •
references/runbook-dns-change.md - •
references/runbook-ansible-pipeline-change.md - •
references/runbook-autoscaling.md