SQS vs SNS vs EventBridge for SAA-C03: How to Decouple an Architecture

FE
FigigExams Team
Senior Network & Security Engineers · 6+ years designing and securing enterprise networks. We build the FigigExams AWS SAA exam. This guide maps to task 2.1 of AWS's SAA-C03 exam guide.
Aligned to the AWS SAA-C03 exam guide · Nov 2026
Try it · free · no credit card

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.

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.

The three at a glance

SQSSNSEventBridge
ModelQueuePub/subEvent bus
DeliveryConsumers pullPushes to subscribersRules route events to targets
FilteringBasicSubscription filter policiesRich content-based rules
Choose forBuffering, decoupling workNotifying many subscribersReacting to AWS or SaaS events

SQS details the exam tests

FeatureMeaning
Standard queueAt-least-once delivery, best-effort ordering
FIFO queueOrdered, exactly-once processing, lower throughput
Visibility timeoutHides a message while one consumer works on it
Dead-letter queueHolds messages that repeatedly fail
Long pollingWaits 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.

  1. Put an SQS queue between the tiers, so the web tier just enqueues and returns.
  2. Run workers in an Auto Scaling group that scales on queue depth, using the number of visible messages.
  3. Set the visibility timeout longer than the job takes, so a slow worker does not cause a duplicate.
  4. 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 saysThink
Decouple tiers, absorb spikesSQS
Strict order, exactly-once processingSQS FIFO
One event, many independent consumersSNS to SQS fan-out
React to AWS service eventsEventBridge
Scheduled triggerEventBridge Scheduler or rule
Replay a real-time streamKinesis Data Streams
Deliver a stream into S3Data Firehose
Messages keep failingDead-letter queue

SQS vs SNS vs EventBridge: practice questions

Five original questions. Each explanation says why the other options fail.

Try it · free · no credit card

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.

Study guides Free exam