This week, we built the complete operational automation and incident response layer of a mature cloud system. Monday was EventBridge and Pipes (the event bus and content-based routing). Tuesday was Automation Documents (procedures-as-code). Wednesday was auto-healing and MAPE-K (self-repair loops). Thursday was ChatOps and Incident Manager (human coordination when repair fails). Today we synthesize: when does each tool apply, and what's the decision tree?
The pattern that emerges is a five-stage pipeline: Detect → Route → Respond → Notify → Learn