Chaos engineering for serverless
summary
Shows how to form serverless hypotheses and actually run them: use AWS Fault Injection Simulator to change Lambda reserved concurrency to zero and auto rollback on CloudWatch alarms, or use SSM automation and a put-parameter action to flip Parameter Store flags. Demonstrates code-level fault injection with failure-lambda and chaos-lambda to add 100–400 ms latency, return 404 on ~50% of requests, or deny S3/Dynamo calls, and confirms experiments run and revert automatically.
AI-written summary · about
chapters (12)
- 0:00Chaos engineering intro
- 1:04What is serverless
- 3:54Serverless weaknesses
- 6:22Fault injection techniques
- 8:12Serverless app setup
- 10:40AWS FIS config manipulation
- 13:07Live config demo
- 16:38Failure Lambda code
- 19:32Live code demo
- 25:08Automating experiments
- 29:57Stop conditions
- 32:51Summary
related talks
43mApplying the Principles of Chaos to Serverless
44mApplying principles of chaos engineering to serverless
49mPerforming Chaos in a Serverless World
24mBreaking Serverless Things on Purpose: Chaos Engineering in Stateless Environments
35mImprove resilience with automated chaos engineering
29mImprove Resilience with automated chaos engineering
26mA proactive approach to resilience in modern apps
42mChaos Engineering: Why Breaking Things Should be Practiced
