Instiq
Chapter 5 · Incident and Event Response·v2.0.0·Updated 6/3/2026·~11 min

What's changed: Deepened DOP-C02 Chapter 5 (added comparison tables, scenarios, FAQs, exam traps, deep-dive paragraphs to each section; localized figures to Japanese)

5.2Auto-Remediation and Runbooks

Key points

Understand automating detect-to-remediate—SSM Automation (runbooks), Config auto-remediation, Lambda remediation, and Auto Scaling self-healing. Correct drift without human intervention.

Auto-remediating incidents lowers MTTR. Runbooks and Config auto-remediation execute predefined fixes mechanically.

5.2.1How auto-remediation works

Diagram of an auto-remediation pipeline: detection (Config rule violation, CloudWatch alarm, GuardDuty) → EventBridge → remediation actions such as SSM Automation runbooks (run predefined fix steps, e.g., make a public S3 private, address unencrypted volumes, isolate an instance) or Lambda; AWS Config attaches remediation actions directly to auto-fix violations; and Auto Scaling auto-replaces unhealthy instances—correction without human intervention.
Auto-remediation and runbooks
  • SSM Automation (runbooks): run predefined fix steps (e.g., make public S3 private, isolate an instance).
  • Config auto-remediation: attach remediation actions to rule violations to auto-fix.
  • Lambda remediation: flexible logic, invoked from EventBridge.
  • Auto Scaling self-healing: auto-replace instances failing health checks.
Exam point

Common on DOP-C02: standard fix steps = SSM Automation runbooks, auto-fix Config violations = Config remediation actions, flexible fixes = Lambda, replace unhealthy = Auto Scaling. Master the detect → EventBridge → remediate (SSM/Lambda) pattern.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.