Study guide
3.4 Systems Manager OpsCenter & Incident Manager Runbooks
AWS Certified Security – Specialty SCS-C03
Track your progress as you read
Finished sections get a check mark.
1 Chapter 0: Getting Started with the SCS-C03 Exam
0.1 SCS-C03 Exam Format, Domains & Study Strategy
2 Chapter 1: Security Monitoring, Alerting & Threat Detection Services
1.1 Workload Monitoring & Health Check Strategies 1.2 Amazon GuardDuty Architecture & Finding Types 1.3 AWS Security Hub & Automated Conformance Assessment 1.4 Amazon Macie & Automated Data Classification
3 Chapter 2: Enterprise Logging Architecture & Analysis
2.1 Multi-Account CloudTrail & Organization Trails 2.2 Amazon Security Lake & OCSF Log Normalization 2.3 Network Telemetry: VPC Flow Logs & Route 53 Resolver Logs 2.4 Troubleshooting Security Telemetry & Log Ingestion 2.5 Analyzing, Normalizing & Correlating Security Logs
4 Chapter 3: Incident Readiness, Response Planning & Automated Runbooks
3.1 Incident Response Planning & Blast Radius Mitigation 3.2 Testing & Validating Incident Response Plans 3.3 Automated Incident Remediation with EventBridge & Step Functions 3.4 Systems Manager OpsCenter & Incident Manager Runbooks
5 Chapter 4: Digital Forensics, Evidence Preservation & Root Cause Analysis
4.1 Forensic Artifact Capture & Chain of Custody 4.2 Threat Containment & Network Quarantine Techniques 4.3 Correlating Events & Root Cause Analysis with Amazon Detective
6 Chapter 5: Edge Protection, WAF & DDoS Mitigation
5.1 CloudFront Security Headers & Origin Access Control 5.2 AWS WAF Architecture & Advanced Rule Sets 5.3 AWS Shield Advanced & DDoS Defense Architectures 5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS
7 Chapter 6: Compute Workload Hardening, Vulnerability Management & GenAI Security
6.1 Golden AMIs & Container Image Hardening Pipelines 6.2 Amazon Inspector Vulnerability Management & Patch Automation 6.3 Generative AI Security: Amazon Bedrock Guardrails & Model Protection 6.4 Instance Profiles, Service Roles & Execution Roles for Compute 6.5 Secure Administrative Access: Session Manager & EC2 Instance Connect
8 Chapter 7: Network Security, Segmentation, Private Connectivity & Encryption in Transit
7.1 Layered Traffic Filtering: SGs, NACLs & AWS Network Firewall 7.2 Hybrid Connectivity Security: VPN, Direct Connect & MACsec 7.3 Zero-Trust Access & Network Access Analysis 7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access 7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access 7.6 Inter-Resource Encryption in Transit: Nitro, EMR, EKS & SageMaker AI
9 Chapter 8: Enterprise Authentication, Federation & Directory Services
8.1 AWS IAM Identity Center & Enterprise IdP Integration 8.2 Amazon Cognito User Pools & Identity Pools 8.3 AWS Security Token Service (STS) & Temporary Credential Workflows 8.4 Troubleshooting Identity & Authentication Failures
10 Chapter 9: Advanced Authorization Architecture & Policy Evaluation
9.1 Complete AWS Policy Evaluation Logic & Decision Flow 9.2 Permission Boundaries & Safe Admin Delegation 9.3 Attribute-Based Access Control (ABAC) with IAM Tags
11 Chapter 10: Least Privilege, Policy Validation & External Access Auditing
10.1 IAM Roles Anywhere & Amazon Verified Permissions 10.2 Auditing External & Unused Access with IAM Access Analyzer 10.3 Analyzing Authorization Failures & Policy Simulation
12 Chapter 11: Cryptographic Services: KMS Architecture & Key Governance
11.1 AWS KMS Architecture, Key Policies & Key Types 11.2 KMS Grants, Encryption Context & Multi-Region Keys 11.3 Imported Key Material (BYOK) & CloudHSM Key Stores
13 Chapter 12: Secrets Management, Sensitive Data Masking & PKI
12.1 AWS Secrets Manager & Systems Manager Parameter Store 12.2 Sensitive Data Masking in Telemetry & Messaging 12.3 AWS Certificate Manager (ACM) & Private CA Architecture
14 Chapter 13: Storage Encryption, Integrity, Lifecycle & Backup Protection
13.1 S3 Encryption Modes & S3 Bucket Keys 13.2 Data Integrity Protection: Object Lock, Vault Lock & Code Signing 13.3 Secure Data Lifecycle, Cross-Account Replication & Backup Vault Lock 13.4 Lifecycle, Backup & Secure Replication Beyond S3: EFS, FSx, DLM, DataSync & Air-Gapped Vaults
15 Chapter 14: Multi-Account Architecture, Organizations & Control Tower Governance
14.1 AWS Organizations Structure, Hierarchy & Resource Control 14.2 AWS Control Tower Landing Zone & Guardrail Framework 14.3 Delegated Administrator Architecture & Root User Governance 14.4 Centralized Resource Sharing with RAM & Service Catalog
16 Chapter 15: Compliance Automation, Infrastructure as Code Security & Auditing
15.1 Infrastructure as Code Security & Multi-Account Deployment 15.2 AWS Config, Conformance Packs & Automated Remediation 15.3 Audit Evidence Collection & Well-Architected Security Reviews
3.4 Systems Manager OpsCenter & Incident Manager Runbooks
Key Takeaways Explain This Topic AI
AWS Systems Manager OpsCenter centralizes operational and security issue management into unified OpsItems, pulling deep context from CloudWatch, Config, and CloudTrail.
OpsCenter mitigates alert fatigue through native deduplication, merging repeating or related operational alerts into a single active OpsItem using source and deduplication strings.
Systems Manager Incident Manager (closed to new customers since November 7, 2025) runs Response Plans that combine on-call contacts, escalation plans, chat channels, and automated SSM runbooks for existing customers.
Amazon Q Developer in chat applications (formerly Amazon Q Developer in chat applications) connects incident channels in Slack or Microsoft Teams to AWS and can run AWS CLI commands, limited by both the channel IAM role and channel guardrail policies.
Incident Manager Post-Incident Analysis (PIM) automatically aggregates chronological timelines of alarms, responder actions, and metrics, converting operational gaps into tracked remediation action items.
Last updated: September 2026
Systems Manager OpsCenter & Incident Manager Runbooks
When a major security incident strikes, technological containment is only half the battle. Responders must also coordinate cross-functional communications, page on-call subject matter experts, manage operational work items, track diagnostic telemetry, and maintain an immutable timeline of events for regulatory post-mortems. Without centralized incident management tooling, responders waste precious time switching between fragmented AWS consoles, misplacing critical context, and causing alert fatigue. AWS Systems Manager OpsCenter and AWS Systems Manager Incident Manager provide the native AWS control plane for operational issue tracking, automated paging escalation, collaborative war rooms, and post-incident analysis.
Important
Service status (2026). AWS stopped accepting new Incident Manager customers on November 7, 2025. Existing customers can keep using it, but it gets no new features. AWS's migration guidance points to OpsCenter for managing operational issues and to partner tools (PagerDuty, Jira Service Management, ServiceNow) for automated paging. AWS Chatbot is now Amazon Q Developer in chat applications . The exam guide names OpsCenter explicitly (skill 2.1.1), so know what each tool does, but design new paging workflows around OpsCenter plus a partner or EventBridge-driven integration.
OpsCenter: Centralized Operational Work Item Management
AWS Systems Manager OpsCenter provides a central operational work management console that aggregates, investigates, and resolves operational and security issues. Rather than requiring engineers to navigate between Amazon CloudWatch alarms, AWS Config non-compliance alerts, and AWS Security Hub findings, OpsCenter normalizes these events into unified work units called OpsItems . +-------------------------------------------------------------+
- | Operational Sources: |
- | • Amazon CloudWatch Alarms |
- | • AWS Security Hub Findings |
- | • AWS Config Non-Compliant Rules |
- | • Amazon EventBridge Custom Rules |
- +-------------------------------------------------------------+
- |
- v
- +-------------------------------------------------------------+
- | OpsCenter Deduplication Engine: |
- | Evaluates source + dedup-string |
- | • If matching open OpsItem exists -> Increment count |
- | • If no matching OpsItem exists -> Create new OpsItem |
- +-------------------------------------------------------------+
- |
- v
- +-------------------------------------------------------------+
- | Unified OpsItem (Operational Context): |
- | • Resource Metadata (AWS Config) |
- | • CloudWatch Metric Graphs & Alarms |
- | • CloudTrail API Logs |
- | • Associated SSM Automation Runbooks |
- +-------------------------------------------------------------+
- The Structure of an OpsItem
An OpsItem captures the complete operational state of an issue:
Title & Description: Clear summary of the operational disruption.
Source: The AWS service or custom system that generated the item (e.g., /aws/securityhub , /aws/cloudwatch ).
Category & Severity: Classified into categories (such as Security , Availability , Performance , Cost ) and given a priority from 1 (highest) to 5 plus a severity label such as Critical, High, Medium, or Low.
Related Resources: Amazon Resource Names (ARNs) of all impacted infrastructure components.
Operational Data: Arbitrary key-value pairs carrying payload diagnostics, finding attributes, or vulnerability scores.
Native Deduplication: Eliminating Alert Fatigue
A common failure in incident response is the "alert storm." When a core network component or database degrades, hundreds of downstream microservices emit cascading alarms. If each alarm generates a distinct ticket, responders become overwhelmed.
OpsCenter resolves this through built-in deduplication :
When an alert attempts to create an OpsItem, OpsCenter evaluates the alert's source and dedup-string .
If an active (status Open or In Progress ) OpsItem already exists with that deduplication key, OpsCenter does not create a new OpsItem .
Instead, the new event is associated with the existing OpsItem (for OpsItems created from EventBridge rules, the dedup string travels in the /aws/dedup operational data key). This condenses thousands of repeating alerts into a single actionable ticket.
Deep Contextual Aggregation
When an engineer opens an OpsItem, OpsCenter automatically surfaces contextual diagnostic data without leaving the console:
AWS Config History: Displays recent configuration changes to the affected resource, highlighting if an unauthorized security group modification occurred immediately before the alert.
CloudWatch Metrics: Inlines performance and traffic graphs directly in the interface.
CloudTrail Logs: Surfaces relevant API calls executed against the target resource.
Associated Runbooks: Recommends specific Systems Manager Automation documents tailored to the OpsItem type (e.g., recommending AWS-RestartEC2Instance or AWSConfigRemediation-ConfigureS3BucketPublicAccessBlock ).
Systems Manager Incident Manager: Crisis Response Orchestration
While OpsCenter manages operational issue backlogs and general work items, AWS Systems Manager Incident Manager is purpose-built for real-time, high-urgency crisis response and automated paging .
Dimension Systems Manager OpsCenter Systems Manager Incident Manager
Primary Purpose Operational work item tracking and issue management Real-time crisis response, paging, and escalation
- Urgency Level All severities (Sev 1 through Sev 5) Focused on high-impact disruptions (Sev 1 and Sev 2)
- Key Primitive OpsItem (work tracking ticket) Incident & Response Plan (active crisis)
- Paging & Escalation Manual notification Automated multi-tier engagement plans (SMS, voice call)
- Collaboration Console notes and status updates Dedicated chat war rooms (Slack, Microsoft Teams)
- Post-Mortem Status transition to Resolved Automated Post-Incident Analysis (PIM) with timeline
- Response Plans: Declarative Crisis Playbooks
At the core of Incident Manager is the Response Plan . A response plan pre-defines the automated workflows executed the moment an incident is declared:
Incident Template: Pre-configures the default title, impact level (1-Critical, 2-High, 3-Medium, 4-Low, 5-Info), summary, and deduplication string.
Chat Channels: Binds the incident to dedicated Amazon Q Developer in chat applications collaboration channels.
Engagements: Specifies the on-call contacts and escalation plans to page.
Automated Runbooks: Designates Systems Manager Automation documents to execute immediately upon incident creation.
- Example: Incident Manager Response Plan CLI Definition {
- "name": "SecOpsCriticalContainmentPlan",
- "displayName": "SecOps Severity 1 Critical Containment Plan",
- "incidentTemplate": {
- "title": "Security Incident: Unauthorized Privilege Escalation",
- "impact": 1,
"summary": "Critical privilege escalation detected. Initiating immediate responder paging and automated host snapshotting.",
- "dedupeString": "SecOps-PrivEscalation"
- },
- "chatChannel": {
- "chatbotSns": [
- "arn:aws:sns:us-east-1:111122223333:SecOpsChatbotIncidentBridgeTopic"
- ]
- },
- "engagements": [
- "arn:aws:ssm-contacts:us-east-1:111122223333:contact/secops-escalation-plan"
- ],
- "actions": [
- {
- "ssmAutomation": {
- "documentName": "AWS-CreateSnapshot",
- "roleArn": "arn:aws:iam::111122223333:role/IncidentManagerAutomationServiceRole",
- "documentVersion": "$DEFAULT"
- }
- }
- ]
- }
- Engagement Plans & Escalation Contacts
When a severity 1 incident occurs at 2:00 AM, broadcasting a generic email to an engineering team is ineffective. Incident Manager provides a structured, time-staged Engagement Plan and on-call rotation framework: +-------------------------------------------------------------+
- | Incident Declared (Severity 1) |
- +-------------------------------------------------------------+
- |
- v
- +-------------------------------------------------------------+
- | Stage 1 (0 Minutes Elapsed): |
- | Send immediate SMS & Mobile Push to Primary On-Call SecOps |
- +-------------------------------------------------------------+
- |
- [Unacknowledged after 5 minutes]
- v
- +-------------------------------------------------------------+
- | Stage 2 (5 Minutes Elapsed): |
- | Initiate Automated Voice Phone Call to Secondary Responder |
- +-------------------------------------------------------------+
- |
- [Unacknowledged after 15 minutes]
- v
- +-------------------------------------------------------------+
- | Stage 3 (15 Minutes Elapsed): |
- | Page Security Operations Director & Cloud Architecture Lead |
- +-------------------------------------------------------------+
- Contact Profiles & Communication Channels
Each responder profile in Incident Manager supports multiple communication channels:
SMS Text Messages: Delivers concise alert summaries.
Voice Phone Calls: Automated voice calls that read incident titles and prompt for tone acknowledgment.
Email Notifications: Delivers full incident context and links.
Mobile App Push Notifications: Alerts the AWS Console mobile application on responder smartphones.
Staged Escalation Schedules
Responders define tiered engagement plans with progressive wait durations:
Stage 1: Contacts the primary on-call engineer immediately via SMS and push notification.
Wait Interval: Incident Manager pauses for a configurable duration (e.g., 5 minutes) while waiting for an acknowledgment token .
Stage 2: If the primary responder does not acknowledge the page within 5 minutes, Incident Manager automatically initiates a voice call to the secondary engineer.
Cross-Team Escalation: If the incident remains uncontained after 15 minutes, the plan escalates ownership to Tier 2 Cloud Infrastructure Leads and Tier 3 Security Principals.
Collaborative Incident Triage with Amazon Q Developer in chat applications
During a crisis, incident responders must communicate in a shared, real-time war room rather than relying on disparate email threads. Incident Manager integrates natively with Amazon Q Developer in chat applications to bridge incident telemetry into Slack or Microsoft Teams .
Dedicated War Room Provisioning
When a Response Plan activates, Amazon Q Developer in chat applications automatically posts incident notifications into designated channels or creates an incident-specific war room channel. Channel members receive real-time updates as metrics spike, alarms transition, or runbooks complete.
Bi-Directional ChatOps Command Execution
Amazon Q Developer in chat applications is not merely a passive notification pipe; it supports bi-directional operational commands . Responders can query AWS infrastructure and execute remediation actions directly from chat:
Acknowledge pages: Responders acknowledge an engagement (by SMS reply, voice prompt, or in the console), which halts further escalation stages.
Inspect Infrastructure: Responders query live resource states (e.g., @aws ec2 describe-instances --filters ... ).
Execute Runbooks: Responders trigger remediation runbooks without opening the AWS Management Console: @aws ssm start-automation-execution --document-name AWS-StopEC2Instance --parameters InstanceId=i-0123456789abcdef0
ChatOps Governance and Channel Guardrails
Executing operational commands from chat introduces security risks if unmonitored. Amazon Q Developer in chat applications enforces strict dual-layer authorization:
Chatbot IAM Execution Role: Defines the maximum AWS permissions granted to the Chatbot service.
Channel Guardrail Policies: An IAM policy applied directly to the chat channel. Even if an engineer has administrative privileges in their personal AWS account, any command executed within the chat channel is restricted by the channel guardrail. This prevents unauthorized users in the chat room from executing destructive commands (such as deleting databases or modifying IAM permissions).
Post-Incident Analysis (PIM / Post-Mortems) & Action Items
The ultimate goal of incident response is learning from failure. When an incident is resolved in Incident Manager, the service transitions to the Post-Incident Analysis (PIM) phase. +-----------------------+ +-----------------------+ +-----------------------+
- | 1. Auto-Timeline | ---> | 2. Structured Review | ---> | 3. Action Items |
- | • Alarms triggered | | • Root cause analysis | | • Create OpsItems |
- | • Pages acknowledged | | • Detection lag | | • Sync with Jira / |
- | • Chatbot commands | | • Containment gaps | | ServiceNow tickets |
- +-----------------------+ +-----------------------+ +-----------------------+
- 1. Automated Chronological Timeline Generation
Manually compiling a timeline after an incident is tedious and error-prone. Incident Manager automatically synthesizes an immutable chronological timeline of the incident by correlating:
The exact timestamp when the initiating CloudWatch alarm fired.
When the incident was declared and which response plan triggered.
When each responder was paged and when they acknowledged the notification.
Every command executed through Amazon Q Developer in chat applications during the triage.
Systems Manager Automation runbook start and completion timestamps.
Manual notes and diagnostic attachments added by responders.
2. Structured Post-Mortem Questionnaire
Incident Manager guides the team through a structured, blameless post-mortem framework:
Incident Summary: What occurred, and what was the customer impact?
Root Cause & Contributing Factors: What technical or procedural factors allowed the incident to occur?
Detection Metrics: What was the Mean Time to Detect (MTTD) ? Did monitoring fire promptly?
Recovery Metrics: What was the Mean Time to Resolve (MTTR) ? Did automated runbooks function as expected?
What Went Well / What Went Poorly: Qualitative assessment of team performance.
3. Action Item Tracking in OpsCenter
Lessons learned are useless if they remain buried in a post-mortem document. Incident Manager allows responders to convert post-incident recommendations directly into tracked action items :
Each action item generates a linked OpsItem in OpsCenter (or syncs bidirectionally with enterprise issue trackers like Jira or ServiceNow ).
Action items track owners, due dates, and remediation progress, ensuring that architectural vulnerabilities and runbook gaps are closed before closing the review.
Investigation Runbooks in SageMaker AI Notebooks
Skill 2.1.1 also lists Amazon SageMaker AI notebooks as a way to build response runbooks. A Jupyter notebook is an executable playbook: each cell holds a documented step (an Athena query over CloudTrail or Security Lake tables, a boto3 call that lists a principal's recent AssumeRole events, a chart of VPC Flow Log bytes), and the output stays next to the step as a record of what the responder saw.
Design points that the exam cares about:
Run notebooks in the security tooling or forensics account , with an execution role that has read access to logs and only the containment permissions the playbook needs.
Put the notebook instance or SageMaker Studio domain in VPC-only mode with VPC endpoints, and encrypt its storage with a KMS key, because notebooks will hold sensitive evidence.
Keep playbooks in Git so they are reviewed and versioned like code, which also guards against the runbook drift covered in section 3.2.
Save notebook outputs to an Object Lock-protected evidence bucket when they become part of an investigation record.
Comparison of Incident Management & Tracking Tools
Feature Systems Manager OpsCenter Systems Manager Incident Manager AWS Health Dashboard
Primary Role Central operational work item management (OpsItems) Real-time crisis response, paging, and war rooms Cloud service health and scheduled maintenance visibility
Core Focus Operational tickets, deduplication, diagnostics High-severity incident management and escalation AWS infrastructure availability and event notifications
Paging / On-Call No native paging (requires external tools) Native multi-tier paging (SMS, voice call, push) No on-call paging (emits EventBridge events)
Chat Integration No direct chat bridge Native chat integration (Slack, Microsoft Teams) Indirect via EventBridge to Amazon Q Developer in chat applications
Post-Mortem Basic ticket resolution Automated Post-Incident Analysis with timeline Service health event summary published by AWS
Automation Link Recommends SSM Automation runbooks Automatically executes SSM Automation runbooks Can trigger EventBridge remediation rules
Exam Tips & Common Traps
Important
Distinguish OpsCenter vs. Incident Manager: This is one of the most frequently tested distinctions in Domain 2. Remember:
Choose OpsCenter when the scenario requires centralizing operational work items (OpsItems) , deduplicating repeating alerts from CloudWatch/Config/Security Hub, or viewing unified resource diagnostic data.
Choose Incident Manager when the scenario requires real-time on-call paging , staged escalation schedules (SMS to voice call) , collaborative chat war rooms via Amazon Q Developer in chat applications , or automated post-incident analysis (post-mortems) .
Warning
Common Trap on Amazon Q Developer in chat applications Permissions: Do not assume that any user in a Slack channel can execute arbitrary AWS commands if Amazon Q Developer in chat applications is configured. Amazon Q Developer in chat applications strictly evaluates Channel Guardrail Policies alongside its IAM execution role. If an action is not permitted by both the IAM execution role and the channel guardrail policy, the command is denied.
Tip
OpsCenter Deduplication Keys: When configuring custom EventBridge rules to create OpsItems, always provide a consistent dedup-string . Without a deduplication string, OpsCenter cannot correlate related alerts, leading to alert flooding during cascading system outages.