01
Landing zones
org-level
LZA-aligned multi-account org. SCPs deny destructive actions in prod. Centralized logging account is the only place CloudTrail and Config write to.
- Org-wide CloudTrail · log-archive S3 with
Object Lock (WORM)
- AWS Config conformance packs (FedRAMP Moderate / NIST 800-53)
- GuardDuty + Security Hub findings aggregated to security account
- Service Catalog products for vetted, pre-approved patterns
02
Infrastructure as code
terraform
100% of prod is Terraform. No click-ops. State in S3 + DynamoDB lock per account. Module library is internal-only — never github.com/... direct refs.
- OpenTofu-compatible · pinned providers · checksum-verified
- tflint + checkov + tfsec + terraform-compliance in CI
- Drift detection runs hourly · auto-opens MR with the diff
- Atlantis-style PR-driven applies behind manual approval gate
03
Network architecture
hub-and-spoke
Transit Gateway hub in the network account. Workload VPCs attach as spokes. No public IPs in prod unless explicitly approved. VPC endpoints for every supported service.
- IPv6 dual-stack from day one · no NAT tax for outbound
- Route 53 Resolver rules + IPAM for non-overlapping CIDRs
- FIPS 140-3 VPC endpoints · TLS 1.3 minimum
- AWS Network Firewall with managed Suricata rule groups
04
Identity & access
least-priv
IAM Identity Center as the front door. Permission sets are Terraform-managed. No long-lived access keys in prod — period. Break-glass roles require ticket + dual-approval.
- STS session limits + ABAC tags scoped to OU
- SCPs deny
iam:CreateAccessKey in workload accounts
- Access Analyzer findings tracked as POA&Ms automatically
- Federation to GitLab CI via OIDC · no static deploy keys
05
Resilience & DR
multi-region
Active-active where the workload supports it, warm-standby where it doesn't. Backup vaults locked with vault-lock. Restore is tested quarterly with a real game-day, not a runbook.
- AWS Backup org policy · cross-region copy · vault-lock immutability
- RDS / Aurora global cluster · 1-min RPO across regions
- Route 53 ARC for traffic shifting · health-check first failover
- Chaos engineering with aws-fis on a schedule
≤ 5 mRPO target
≤ 15 mRTO target
Qrestore tested
06
Confidential compute
future-ready
Nitro Enclaves for workloads that need attested, isolated execution — KMS key material never leaves the enclave. Foundation for FedRAMP High + IL5 trajectories.
- Nitro Enclaves with KMS attestation-based grants
- EC2 with NitroTPM + UEFI Secure Boot for cleared baselines
- Outposts & Snowball Edge for tactical / disconnected scope
- Wavelength + Local Zones evaluated for edge AI inference