A Journey to Automated Infrastructure
summary
eVestment migrates to AWS and automates everything in 6 months migration, replacing VMs with Docker on ECS, moving .NET Framework to .NET Core, and enforcing 100% infrastructure as code with Terraform plus immutable infrastructure so instances are killed and replaced instead of patched. CI moves to Jenkins shared libraries and a cross‑platform CLI wrapper, monitoring centralizes in DataDog. Outcome: a single‑button cutover with zero production issues, ~60 microservices, and 1,800 infra deployments yielding ~99.99% uptime.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:28Who we are
- 1:31Our Stax
- 5:15AWS Migration
- 7:11DevOps
- 7:27Engineering vs DevOps
- 8:52Project Llama
- 10:20Who owns Llama
- 11:11Using Terraform
- 11:30Using Synthetics
- 11:54Modularity
- 12:32Terraform Modules
- 14:12Human Gate
- 14:26Local Development Experience
- 15:57Demo
- 16:44Example
- 17:00Test Kitchen
- 18:38Jenkins Shared Library
- 19:32Frontend
- 21:03Shared Library Human Gate
- 23:07Contact Information
related talks
40mInfrastructure as code in action - How we built a platform during a cloud migration
50mImmutable Infrastructure as Code. True story
01h 03mContinuous Security in the Cloud
01h 02mTransforming IT pros to DevOps gurus: Ssecure your new tech stacks
49mHardware to AWS, EC2 to EKS: Two Years, Two Epic Migrations
29mTaming the Hybrid Beast with DevOps
01h 02mTools and Techniques for Infrastructure as Code
25mEnterprise Deployment to Azure and AWS in Azure DevOps