Chaos Engineering Panel
summary
Panel outlines concrete first steps: verify top 10 alerts and measure time to detect and respond, run small game days and fire drills, and iterate from sandbox to non‑prod to production. Tooling strategy mixes open source, vendor evaluations and built an MVP when controls block imports; AWS Fault Injection Simulator appears as a new option. Biggest gaps are observability holes and cross‑team coordination; recommended skills are cloud infra, Python, SRE practices and threat‑aware hypotheses.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:43Intro Christina Yakomin
- 1:00Intro Courtney Nash
- 1:31Intro Kelly Shortridge
- 2:01Intro David Lavezzo
- 2:20Challenges in organizations in adopting CE
- 5:01First steps to take to start a CE program
- 8:50How does CE scale?
- 12:07Myths & misconceptions of CE
- 19:34Favorite CE tools
- 23:29Strategies for testing systems
- 31:47Coordination across teams
- 33:47What skills sets are needed in a CE team?
- 39:15Security chaos engineering
- 44:00Takeaways
- 47:45Outro
related talks
49mSpeaker Panel - Day 1
47mChaos Engineering Bottom Up
57mChaos Engineering Primer
18mChaos Engineering: Break It On Purpose
22mLooking Back to Look Forward
52mPanel Discussion
27mChaos Engineering: The Path to Reliability
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure