Hands-on with the Terraform Module for AWS Landing Zone
summary
A hands‑on tour of a public Terraform module for AWS Landing Zone shows concrete rules and outcomes: the registry + GitHub repo provide about 80 components implemented as components as immutable microservices with a convention of provider per account per region; variables map providers → component instances, TF state can go to S3, and an import file automates terraform import of existing resources. Demo runs terraform plan/apply and CI via GitHub → CodeBuild for automated plan/apply; the live demo has a partial failure and AWS SSO integration remains a common pain point.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:21What is AWS Landing Zone
- 1:50Issues with AWS Landing Zone
- 3:35Who am I
- 4:01Agenda
- 5:50Providers
- 7:57Components
- 10:13Defining Provider
- 14:21Summary
- 21:51Architecture
- 25:59Naming Convention
- 30:00Automation Repository
- 32:03Demo
- 34:08Login to Universe
- 34:29Chat
- 35:02QA
- 35:22Permissions
- 36:32Integration with Github
- 37:43Terraform as an application
- 38:29How comfortable are you with Terraform
- 40:31Transit Gateway
- 41:04Questions
related talks
26mHands-On Terraform Module for AWS Landing Zone
10mInfrastructure as a Code Best Practices with Terraform
45mThe Automation of a Landing Zone
55mBest practices
40mFrom Launch Pad to Landing Zone: DevOps Governance with Terraform
33mBuilding applications with infrastructure as code
01h 25mWorkshop: Infra-as-Code & Terraform
41mScale infrastructure operations with HCP Terraform self-service workflows