Skip to content

SYSTEM Cited by 3 sources

Amazon SNS

Amazon SNS (Simple Notification Service) is AWS's managed pub/sub fanout messaging service. Publishers post to a topic; subscribers (SQS queues, Lambda functions, HTTP endpoints, email, mobile push) each receive their own copy. Commonly paired with systems/aws-sqs as the fanout half of a topic → queue-per-consumer pipeline.

Role for this wiki

SNS appears as the fanout primitive in AWS-native producer/consumer pipelines. The canonical shape is S3 event → SNS topic → SQS queue-per-consumer, letting each downstream subscriber control its own queue depth + retention without affecting others.

SNS/SQS pairs as anti-pattern at org scale

Per-integration SNS topics + SQS queues between services is a natural first step for introducing async decoupling, but Amazon Key explicitly names it as "implemented on an ad-hoc basis, lacking standardization and creating additional maintenance overhead". At fleet scale SNS/SQS pairs become pub/sub without governance — no shared schema registry, no content-based routing rules, no subscriber-provisioning scaffolding. EventBridge is AWS's answer for org-scale event-driven architectures: one bus with content-based routing rules + a schema registry + reusable subscriber constructs (patterns/single-bus-multi-account, patterns/reusable-subscriber-constructs, patterns/client-side-schema-validation). SNS remains the right primitive for narrower fanout pipelines (S3 event → SNS → SQS per consumer) and as an EventBridge target.

Seen in

Last updated · 200 distilled / 1,178 read