Immutable Infrastructure as Code. True story
summary
Moves a legacy PHP fleet into immutable infrastructure described as code by building AMIs and Docker images, using Packer and cloud‑init for bake time config, Terraform for datacenter wiring, Jenkins as CI/CD and AWS managed services (RDS, ElastiCache) for state. Results: reproducible instances instead of drift, kill‑and‑replace repairs, and a companywide Jenkins with 300+ pipelines; initial Jenkins setup costs about two months for two people. Deploy flow becomes Terraform apply plus Jenkins deploy from a repo .infrastructure folder and it demonstrably reduces toil and outage time.
AI-written summary · about
chapters (23)
- 0:00Intro
- 3:47Project takeover from outsourcing company
- 5:00State of the project after takeover
- 6:26After some refactoring... We've got typical setup
- 7:08Issues we noticed
- 9:03Configuration Synchronisation problem, in short
- 11:41Blue sky vision
- 13:33What is immutable infrastructure?
- 14:31Why go Immutable?
- 16:18How to achieve this?
- 18:57Main tools we use
- 22:10Orchestration
- 24:07OS level setup
- 29:28Everything as code: full list
- 34:38Lessons learned
- 35:42Single fact you could memorise here
- 38:33How Terraform is different to Ansible/Chef/Puppet
- 39:02Imperative VS Declarative infrastructure code
- 40:08Why go Declarative?
- 41:56Deploy with Terraform
- 44:41Things that work for 3 teams - doesn't work for 10
- 47:30DevOps on Call & transparent SLAs
- 48:10Encourage feedback
related talks
47mImmutable Infrastructure GitHub + Terraform + Packer
46mImplementing Infrastructure as Code
39mAutomating Immutable Infrastructure With Packer & Terraform
46mHow IaaS and Immutable Infrastructure Improved Our Way to Deploy
01h 02mTools and Techniques for Infrastructure as Code
15mInfrastructure as a Code: Best Practices and Myths
46mThink of your infrastructure as code
01h 02mTools and Techniques for Infrastructure as Code