Captial One's Newly Designed Fully Automated, Scalable, and...
summary
Captial One's Newly Designed Fully Automated, Scalable, and Regionally Fault-tolerant Chef platform claims a concrete redesign: move from five stacks to reduced stacks from five to two, put Chef servers behind ALBs in ASGs across three AZs, migrate cookbooks into an RDS-backed cluster, and replace EBS failover with Lambda-driven read-replica promotion plus Route53 latency failover. Built elasticsearch clusters, automated rehydration with canary ASG deployments for zero downtime, measures regional failover under ~10 minutes, and adds Smart Ops/CloudWatch automation after two real replication outages.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:31History of Chef
- 3:31Legacy Chef Architecture
- 4:45Rehydration
- 10:45Health Checks
- 12:23Node Cleanup
- 14:38Event Subscriptions
- 18:29Canary Deployment
- 21:52Simulate a Regional Failover
- 23:43Multi-Branch Pipeline
- 25:36Bootstrap a Linux Box
- 29:15Artifact Conflict
- 35:57Future Plans for Chef
- 38:54Chamber of Secrets
- 39:43Are You Running One Organization or Do You Have Multiple Organizations
related talks
33mScaling Chef Emotionally
54mTableau Server on AWS enables analytics agility for Capital One
49mAutomation in Deployment on Hybrid Hosting and Private Cloud Environments
34m"Acing" Infrastructure Testing with Chef
25mCooking with Chef - Your servers will thank you
48mManaged Chef in the Cloud: Introducing AWS OpsWorks for Chef Automate
14mExpect the unexpected: Building resilience with AWS
42mPlanning To Fail