People, process, and technology for ILM and SLM adoption
summary
A practical framework lays out concrete building blocks: monitoring and observability for audit and drift detection, modularization plus access control to limit blast radius, and standardization and remediation so one template can roll out a patch everywhere. Using Terraform, Vault, Boundary, Packer and Waypoint, the workflow moves toward as code orchestration and a system of record that lets teams assess blast radius. A concrete result: bespoke datacenter fixes took four weeks versus under a day after enforcing templates and immutability. The goal is immutability and ephemerality with short‑lived credentials and blue‑green replacements.
AI-written summary · about
chapters (8)
- 0:00Introduction to ILM and SLM
- 3:08Foundations of monitoring and observability
- 6:17Modularization and access control
- 9:45Standardization and remediation
- 14:18Immutability and ephemerality
- 18:50Infrastructure as code for scale
- 21:59Systems of record and visibility
- 24:27Summary and next steps
related talks
41mScaling Infrastructure as Code
22mLaunch Control - Automating a Security Baseline...
33mSecurity scans for terraform templates
29mBreaking Down the TofuLith. How We Reduced Lead Times for Multi-Tenant Infra Changes...
25mRebuilding Infrastructure (as Code)
27mCase Study: Re-Thinking Our Infrastructure Tooling
42mLessons Learned as a DevOps Consultant
44mEvolution of Infrastructure Management