Instiq
Chapter 5 · Incident and Event Response·v2.0.0·Updated 6/3/2026·~10 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.3Notification and Escalation

Key points

Understand incident notification and operations—SNS, EventBridge, Systems Manager Incident Manager, Chatbot (Slack/Teams), and dead-letter queues (DLQ). Reach the right people reliably and coordinate response.

Beyond detection and remediation, notifying the right people and escalating matters. SNS and Incident Manager coordinate response.

5.3.1Notification and incident management

Diagram of notification and escalation: EventBridge/SNS receive alarms/events; SNS fans out notifications to Email/SMS/HTTP/Lambda; AWS Chatbot relays ops notifications to Slack/Teams; serious incidents are coordinated by Systems Manager Incident Manager following an escalation plan (on-call contacts, response plan, automated runbooks); and messages that fail delivery move to a dead-letter queue (DLQ) for later reprocessing.
Notification and incident management
  • SNS: fan out notifications to Email/SMS/HTTP/Lambda.
  • Chatbot: relay ops notifications/alarms to Slack/Teams.
  • Incident Manager: coordinate escalation plans, response plans, and on-call for major incidents.
  • DLQ: park messages that fail delivery/processing for later reprocessing.
Exam point

Common on DOP-C02: notification fan-out = SNS, Slack/Teams = Chatbot, major-incident coordination/on-call = Incident Manager, park failed messages = DLQ. Configure DLQs so failed Lambda/SQS processing is not lost.

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.