Study guide
2.2 Notification Architecture & Alarm Invocation
AWS Certified CloudOps Engineer – Associate SOA-C03
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Monitoring & Observability Infrastructure
1.1 Configuring Workload Observability 1.2 CloudWatch Agent Architecture & Deployment 1.3 Metric Alarms, Anomaly Detection & Composite Alarms
2 Chapter 2: Alarms, Dashboards & Event-Driven Remediation
2.1 CloudWatch Dashboards & Multi-Account Visibility 2.2 Notification Architecture & Alarm Invocation 2.3 Amazon EventBridge Rules, Event Buses & Troubleshooting 2.4 Automated Remediation with Systems Manager & Lambda
3 Chapter 3: Performance Optimization for Compute, Storage & Databases
3.1 EC2 & Compute Performance Optimization 3.2 Amazon EBS Performance Metrics & Volume Tuning 3.3 S3 Performance Strategies & Data Transfer 3.4 Shared Storage (EFS/FSx) & Database Performance
4 Chapter 4: Compute & Database Scalability and Elasticity
4.1 EC2 Auto Scaling Policies & Elasticity 4.2 Auto Scaling Advanced Operations: Warm Pools & Lifecycle Hooks 4.3 Dynamic Scalability Through Caching 4.4 Managed Database Scaling: RDS, Aurora & DynamoDB
5 Chapter 5: High Availability, Fault Tolerance & Load Balancing
5.1 Elastic Load Balancing (ALB/NLB) Configuration & Troubleshooting 5.2 Route 53 Health Checks & DNS Failover 5.3 Multi-AZ Architecture & Fault-Tolerant Deployments
6 Chapter 6: Backup, Data Protection & Disaster Recovery
6.1 Centralized Backup Automation & AWS Backup 6.2 Database Restore Strategies & RTO/RPO Management 6.3 Storage Versioning, Replication & Immutability 6.4 Disaster Recovery Patterns & Multi-Region Resilience
7 Chapter 7: Infrastructure as Code with CloudFormation & AWS CDK
7.1 CloudFormation Foundations & Resource Modeling 7.2 Managing Stacks, Drift Detection & Change Sets 7.3 Infrastructure as Code with AWS CDK 7.4 Identifying & Remediating Deployment Failures
8 Chapter 8: Multi-Account Provisioning, Containers & Third-Party IaC
8.1 Golden Images with EC2 Image Builder & Amazon ECR 8.2 Multi-Account & Multi-Region Resource Sharing 8.3 Deployment Strategies & Container Deployments 8.4 Third-Party Automation with Terraform & Git Workflows
9 Chapter 9: Systems Manager & Event-Driven Operations Automation
9.1 AWS Systems Manager Core Management & Run Command 9.2 Systems Manager Patch Manager & Session Manager 9.3 Event-Driven Operations Automation
10 Chapter 10: Identity, Access Management & Governance
10.1 Advanced IAM Policies, Roles & Policy Conditions 10.2 Auditing Access with CloudTrail Lake & IAM Access Analyzer 10.3 Multi-Account Security: Organizations, SCPs & Identity Center 10.4 Compliance Enforcement with AWS Config & Conformance Packs
11 Chapter 11: Data Security, Encryption & Vulnerability Management
11.1 Data Classification & Amazon S3 Security 11.2 Encryption at Rest with AWS Key Management Service (KMS) 11.3 Encryption in Transit with AWS Certificate Manager (ACM) 11.4 Secrets Management & Centralized Security Findings
12 Chapter 12: VPC Architecture, Endpoints & Network Protection
12.1 VPC Core Architecture, Subnetting & High Availability NAT 12.2 Private Network Connectivity: VPC Endpoints & Peering 12.3 Network Protection & Edge Security Auditing
13 Chapter 13: DNS, Route 53 Routing & Content Delivery
13.1 DNS Architecture & Route 53 Resolver for Hybrid Clouds 13.2 Route 53 Advanced Routing Policies & Query Logging 13.3 Global Content & Service Distribution: CloudFront & Global Accelerator
14 Chapter 14: Network Troubleshooting, Traffic Analysis & Hybrid Connectivity
14.1 VPC Configuration Troubleshooting & Analysis Tools 14.2 Network Traffic Analysis: VPC Flow Logs & Log Analytics 14.3 CloudFront Caching & Hybrid Connectivity Troubleshooting
2.2 Notification Architecture & Alarm Invocation
Key Takeaways Explain This Topic AI
CloudWatch alarms strictly require Amazon SNS Standard topics as alarm action destinations; SNS FIFO topics are not supported for CloudWatch alarm notifications.
SNS Standard topics enable the fan-out pattern to simultaneously broadcast alerts to Amazon SQS Standard queues, AWS Lambda functions, HTTPS webhooks, SMS, and email endpoints; SQS FIFO queues can only subscribe to an SNS FIFO topic.
SNS topic resource-based access policies must explicitly grant the cloudwatch.amazonaws.com service principal permission to perform sns:Publish, restricted by aws:SourceArn or aws:SourceAccount to prevent confused deputy exploits.
When an SNS topic is encrypted using AWS KMS, customer managed keys (CMKs) must be used instead of the default aws/sns key, and the KMS key policy must grant kms:GenerateDataKey* and kms:Decrypt permissions to cloudwatch.amazonaws.com.
SNS subscription filter policies evaluate message attributes to deliver alerts selectively to appropriate channels (e.g., critical alerts to PagerDuty webhooks, warning alerts to Slack), while subscription dead-letter queues (DLQs) capture undelivered notifications after retry exhaustion.
Last updated: September 2026
2.2 Notification Architecture & Alarm Invocation
Amazon Simple Notification Service (Amazon SNS) serves as the primary notification and alert-routing backbone for AWS operational monitoring. When Amazon CloudWatch alarms detect threshold violations or anomaly band breaches, they invoke automated actions by publishing messages to Amazon SNS topics. From there, SNS fans out notifications to diverse human and automated endpoints. For CloudOps engineers preparing for the SOA-C03 exam, deep knowledge of SNS topic types, resource access policies, KMS encryption configurations, delivery retry mechanisms, subscription filter policies, and dead-letter queues (DLQs) is essential.
Amazon SNS Topic Architecture: Standard vs. FIFO
Amazon SNS supports two distinct topic types designed for different architectural workloads:
- Architectural Dimension SNS Standard Topic SNS FIFO Topic
- Message Ordering Best-effort message ordering Strict FIFO (First-In, First-Out) ordering
- Deduplication At-least-once delivery (duplicates possible) Exactly-once delivery via Message Deduplication ID
Throughput Capacity Nearly unlimited messages per second Up to 3,000 messages/sec (or 30,000/sec with high throughput mode)
Supported Subscribers SQS Standard queues, Lambda, HTTP/S, Email, SMS, mobile push (SQS FIFO queues cannot subscribe to a Standard topic) SQS FIFO queues, plus SQS Standard queues since September 2023
CloudWatch Alarm Support Fully supported as alarm actions Not supported as CloudWatch alarm targets
A critical exam distinction is that CloudWatch alarms cannot publish actions directly to SNS FIFO topics . If an alarm action specifies an SNS FIFO topic ARN, the CloudWatch alarm configuration will fail validation. Therefore, all operational alert-routing topologies rely on SNS Standard topics .
Standard topics utilize the asynchronous fan-out pattern . A single alarm publication to an SNS topic can simultaneously broadcast messages across thousands of heterogeneous subscriber protocols:
Amazon SQS Queues : Buffering incident records for asynchronous processing by backend ticketing systems.
AWS Lambda Functions : Executing custom remediation scripts, querying CMDBs, or updating incident dashboards.
HTTPS Webhooks : Forwarding alert payloads to incident management platforms like PagerDuty, Opsgenie, or Slack/Microsoft Teams gateways.
Email (SMTP) & SMS : Delivering direct text notifications to on-call system administrators.
Security, Access Control & KMS Encryption
Because Amazon SNS topics are communication gateways, their access must be strictly governed by resource-based SNS Topic Access Policies . By default, only the topic owner can publish messages. When a CloudWatch alarm triggers, the CloudWatch service publishes to the SNS topic on the user's behalf.
To allow CloudWatch alarms to publish to an SNS topic without exposing the topic to unauthorized third parties or falling victim to the confused deputy problem , the topic policy must explicitly permit the cloudwatch.amazonaws.com service principal, restricted by the aws:SourceArn or aws:SourceAccount condition: {
- "Version": "2012-10-17",
- "Statement": [
- {
- "Sid": "AllowCloudWatchAlarmsToPublish",
- "Effect": "Allow",
- "Principal": {
- "Service": "cloudwatch.amazonaws.com"
- },
- "Action": "sns:Publish",
- "Resource": "arn:aws:sns:us-east-1:123456789012:cloudops-alarms-topic",
- "Condition": {
- "ArnLike": {
- "aws:SourceArn": "arn:aws:cloudwatch:us-east-1:123456789012:alarm:*"
- }
- }
- }
- ]
- }
- Server-Side Encryption (SSE) with AWS KMS
Enterprise security standards often require server-side encryption at rest for SNS topics. SNS integrates with AWS Key Management Service (KMS) using customer managed keys (CMK) or AWS managed keys ( aws/sns ).
A frequent scenario tested on the CloudOps exam involves CloudWatch alarms failing to deliver notifications to encrypted SNS topics . When an SNS topic is encrypted with the default AWS managed key ( aws/sns ), CloudWatch alarms cannot publish to it. This occurs because the default aws/sns KMS key policy cannot be modified to grant permissions to external service principals like cloudwatch.amazonaws.com .
To successfully publish alarm notifications to an encrypted SNS topic, organizations must use a customer managed KMS key (CMK) and update its key policy to explicitly grant the cloudwatch.amazonaws.com service principal permissions to generate data keys and decrypt them: {
- "Sid": "AllowCloudWatchKMSAccess",
- "Effect": "Allow",
- "Principal": {
- "Service": "cloudwatch.amazonaws.com"
- },
- "Action": [
- "kms:GenerateDataKey*",
- "kms:Decrypt"
- ],
- "Resource": "*",
- "Condition": {
- "ArnLike": {
- "aws:SourceArn": "arn:aws:cloudwatch:us-east-1:123456789012:alarm:*"
- }
- }
- }
- Delivery Retries, Dead-Letter Queues (DLQs) & Message Filtering
When SNS attempts to deliver an alarm message to an HTTPS endpoint or webhook, network partitions or target downtime may cause delivery failures. SNS manages transient failures through configurable delivery retry policies .
For HTTP/S endpoints, SNS executes a four-phase retry protocol:
Immediate Retries : Attempts delivery immediately without delay.
Linear Backoff : Retries at steady, short intervals.
Exponential Backoff : Gradually doubles retry wait times.
Geometric Backoff : Applies a multiplier to delay intervals until the maximum retry limit (up to 100 attempts over several hours or days) is reached.
If an endpoint remains unreachable after exhausting all retries, the message is permanently dropped unless a Dead-Letter Queue (DLQ) is attached. In Amazon SNS, DLQs are Amazon SQS queues attached directly to specific subscriptions , rather than to the topic itself. If a subscriber webhook fails, SNS offloads the failed message, headers, error codes, and delivery timestamps to the SQS DLQ for diagnostic analysis and replay.
Message Filtering with Subscription Filter Policies
By default, every subscriber to an SNS topic receives every message published. In large-scale operations, broadcasting all alerts to all channels creates alert fatigue. CloudOps engineers implement SNS Subscription Filter Policies to filter messages based on message attributes.
When a message is published with attributes such as Severity = "CRITICAL" or Service = "RDS" , subscribers define filter policies in JSON: {
- "Severity": ["CRITICAL", "HIGH"],
- "Environment": ["Production"]
- }
Subscribers whose policies do not match the published attributes are bypassed entirely without incurring Lambda execution fees, webhook spam, or email flooding.
Operational Scenario: Tiered Incident Routing
A typical enterprise operational architecture routes alerts based on severity and destination requirements:
Tier 1 (Critical Severity) : An SNS topic filters for Severity = "CRITICAL" . Subscriptions dispatch immediately to an on-call PagerDuty HTTPS webhook and an automated remediation Lambda function. The subscription is backed by an SQS DLQ to prevent dropped incidents during API throttling.
Tier 2 (Warning Severity) : An SNS topic filters for Severity = "WARNING" . Messages route to an Amazon SQS queue polled by a corporate chat application (e.g., Slack or Teams) and a daily operational digest email.