SQS vs SNS vs EventBridge for SAA-C03: How to Decouple an Architecture
Know this topic? Test it on a full SAA-C03 paper
A complete SAA-C03 practice exam: 65 questions in 130 minutes, an explanation on every item and an Exam Coach report that ranks your weakest domains.
AWS-SAA-FULL
Try a free AWS SAA exam
Already have an account? Log in to redeem
Use SQS when a consumer should pull work from a queue at its own pace. Use SNS to push one message to many subscribers. Use EventBridge to route events by content, including from AWS services and SaaS sources. Combine SNS with SQS for the fan-out pattern. Use Kinesis for ordered, replayable real-time streams.Checked against AWS's published exam guide on 9 November 2026.
In this guide
The three at a glance
| SQS | SNS | EventBridge | |
|---|---|---|---|
| Model | Queue | Pub/sub | Event bus |
| Delivery | Consumers pull | Pushes to subscribers | Rules route events to targets |
| Filtering | Basic | Subscription filter policies | Rich content-based rules |
| Choose for | Buffering, decoupling work | Notifying many subscribers | Reacting to AWS or SaaS events |
SQS details the exam tests
| Feature | Meaning |
|---|---|
| Standard queue | At-least-once delivery, best-effort ordering |
| FIFO queue | Ordered, exactly-once processing, lower throughput |
| Visibility timeout | Hides a message while one consumer works on it |
| Dead-letter queue | Holds messages that repeatedly fail |
| Long polling | Waits for messages, reducing empty responses and cost |
Where Kinesis fits
Kinesis Data Streams holds an ordered stream that multiple consumers can read and replay, which suits clickstreams and real-time analytics. SQS deletes a message once it is processed.
A worked scenario: decoupling an order flow
Requirement: a web tier accepts orders faster than the back end can process them, and orders must not be lost during a spike.
- Put an SQS queue between the tiers, so the web tier just enqueues and returns.
- Run workers in an Auto Scaling group that scales on queue depth, using the number of visible messages.
- Set the visibility timeout longer than the job takes, so a slow worker does not cause a duplicate.
- Add a dead-letter queue for orders that repeatedly fail.
Scaling on CPU is the trap here. Queue depth is the metric that reflects the backlog.
More details that get tested
- SQS Standard can deliver a message more than once, so consumers should be idempotent.
- SQS retains messages for up to 14 days, with a default of 4 days.
- A delay queue postpones delivery of new messages.
- Amazon Data Firehose loads streaming data into destinations such as S3 and Redshift. Kinesis Data Streams is for custom real-time consumers.
How the exam words it
| If the question says | Think |
|---|---|
| Decouple tiers, absorb spikes | SQS |
| Strict order, exactly-once processing | SQS FIFO |
| One event, many independent consumers | SNS to SQS fan-out |
| React to AWS service events | EventBridge |
| Scheduled trigger | EventBridge Scheduler or rule |
| Replay a real-time stream | Kinesis Data Streams |
| Deliver a stream into S3 | Data Firehose |
| Messages keep failing | Dead-letter queue |
SQS vs SNS vs EventBridge: practice questions
Five original questions. Each explanation says why the other options fail.
Your free AWS SAA exam code is ready
Sit the full SAA-C03 paper against the real 130-minute clock. AWS SAA is $39 once, lifetime, future versions included.
AWS-SAA-FULL
Redeem the code
Already have an account? Log in to redeem
Frequently asked questions
What is the difference between SQS and SNS?
SQS is a queue where consumers pull messages. SNS is pub/sub, pushing each message to all subscribers. They are often combined in a fan-out pattern.
When should I use EventBridge instead of SNS?
When you need content-based routing, or events from AWS services and SaaS applications.
What is the difference between SQS and Kinesis?
SQS decouples work, and each message goes to one consumer before being deleted. Kinesis keeps an ordered stream that multiple consumers can read and replay.
What is the difference between Kinesis Data Streams and Data Firehose?
Kinesis Data Streams is a real-time stream with custom consumers and replay. Amazon Data Firehose delivers streaming data to S3, Redshift or OpenSearch in near real time with no consumer code to write.