Multi Region Deployments with AWS CI/CD and Terraform
summary
Builds a repeatable multi-region AWS deployment using Terraform and AWS CI/CD with a central tooling account and a multi-account boundary model. Uses git tags like Dev/EU/research/v1 to trigger a versioned S3 backend, TF Lint and Checkov scans, then terraform plan/apply; state is split per-region per-environment so failures don’t cascade. Pipelines are deployed by Terraform themselves and run as the pipeline as golden source for changes; sample code and demos are available in an open GitHub repo.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 1:06Why multi-region deployments
- 3:15Blueprints and layered architecture
- 5:42Pipeline design and workflow
- 9:18Multi-account strategy
- 11:04Regional pipeline isolation
- 12:28Authoritative pipeline source
- 13:36Final architecture overview
- 14:46Q&A disaster recovery
- 15:52Q&A sustainability
- 16:14Q&A Terraform alternatives
related talks
35mMulti Region Terraform Deployments
25mEnterprise Deployment to Azure and AWS in Azure DevOps
27mOptimizing Terraform integration inside GitLab CI/CD pipelines
27mBuilding Multi-region CI/CD Pipelines with a DevOps Mindset
19mSynchronization of Infrastructure Provisioning & Application Deployments
31mCommodified IaC using Terraform Cloud
10mInfrastructure as a Code Best Practices with Terraform
39mTerraform Practices to Enable Infrastructure Scaling