Why segmenting your infrastructure into tiers makes your infra design better
summary
Presents a concrete three‑tier pattern: tier zero VPC and network foundations, tier one shared platform (EKS clusters, observability, AMIs) and tier two application resources (RDS, KMS) with explicit ownership per tier. Uses Terraform/Pulumi/CDK primitives, recommends flat inputs and outputs (VPC ID, subnet IDs, IAM role ARNs) and passing state via workspace import or SSM. Claim: tiering cuts IaC deployment time and blast radius, reduced a full cluster build to a 7‑minute deploy in demos, and enforces clear ownership.
AI-written summary · about
chapters (10)
- 0:00Infrastructure tiering intro
- 1:04Who I am and conference context
- 3:10Infrastructure bucketing problems
- 4:14What makes infrastructure taring different
- 5:59Three-tier design overview
- 7:42Tier zero resources
- 9:05Tier one resources
- 10:09Tier two resources
- 11:55Benefits of tiering
- 13:43Q&A
related talks
10mInfrastructure as a Code Best Practices with Terraform
41mScaling Infrastructure as Code
38mApplication-Driven Infrastructure Deployment
16mDeclarative vs programmatic IaC
19mSynchronization of Infrastructure Provisioning & Application Deployments
23mUnleashing Potential Across Teams: Infrastructure as Code
05mLessons learned from building a cloud-native platform
53mProvisioning Cloud Infrastructure+Terraform