Arkinu
AWS service comparison

Amazon EventBridge vs Amazon SNS: differences and when to use each

Amazon EventBridge
Amazon SNS

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Application Integration

Amazon EventBridge

Serverless service that connects components using events: it receives events from AWS services, your own applications, and third-party software, filters and transforms them, and delivers them to the appropriate targets. It includes EventBridge Scheduler for scheduling tasks with cron or rate expressions.

Exam phrases that point here

  • «automatically react when an AWS resource changes state»

    Many AWS services send their events to the account's default event bus; a rule with an event pattern detects the change (for example, an EC2 instance moving to stopped) and triggers a target, with nothing for you to poll.

    When not: If the requirement is to find out who made an API call for auditing, the answer points to AWS CloudTrail; if the reaction depends on a metric crossing a threshold, an Amazon CloudWatch alarm is a better fit.

  • «route events to different targets based on their content»

    The rules on a classic bus (or the filters on each subscriber in the new Custom Event Bus) compare every event against a pattern on its fields and send only the matching ones to their target; a single event can reach several targets.

    When not: If the core requirement is to fan out the same message to a very large number of subscribers, including email, SMS, or mobile push notifications, Amazon SNS is usually a better fit; if messages must be held until a consumer pulls them at its own pace, the key component is usually Amazon SQS.

  • «receive events from a third-party SaaS application without writing polling code»

    SaaS partners integrated with EventBridge publish to a partner event source which, once associated with an event bus in your account, lets you apply rules to those events.

    When not: If the provider is not an EventBridge partner, another ingestion mechanism is needed; and if the requirement is to transfer data in bulk from a SaaS application to a destination such as Amazon S3, the answer points to Amazon AppFlow.

  • «run a task on a schedule without managing servers»

    EventBridge Scheduler (or, previously, scheduled rules) invokes an AWS target based on a cron, rate, or one-time expression, with configurable retries.

    When not: EventBridge only triggers the task: the target does the work. If the question is about where a long-running process runs, the answer lies in compute (for example, AWS Batch or Amazon ECS), not in the scheduler.

  • «reprocess past events after fixing a bug»

    On a classic bus, Archive and Replay stores events and resends them later. The new Custom Event Bus retains them for 1 to 365 days, and a subscriber can start reading from a point in the past. It is useful for debugging, recovering, or populating a new target.

    When not: If it is real-time streaming data (clicks, telemetry) that several applications process and reread, Amazon Kinesis Data Streams is usually a better fit. Note that ordering and rereading alone no longer rule out EventBridge, because the new Custom Event Bus retains events and delivers them in order per group.

  • «connect a source to a single target, with filtering and enrichment, without integration code»

    EventBridge Pipes connects a source (such as an SQS queue or a Kinesis or DynamoDB stream) to a target, with optional filtering and enrichment in between.

    When not: If there are many sources and many targets, the pattern is an event bus, not a pipe; and if it is enough for AWS Lambda to read from a queue, the Lambda event source mapping already solves it.

Often paired with

  • AWS Lambda
  • AWS Step Functions
  • Amazon SQS
Study Amazon EventBridge →

Application Integration

Amazon SNS

Managed publish/subscribe service: publishers send messages to a topic, and Amazon SNS delivers them to all of its subscribers, such as Amazon SQS queues, AWS Lambda functions, HTTP(S) endpoints, email, or SMS. It handles distributing the same message to many destinations (fan-out) and sending notifications.

Exam phrases that point here

  • «send the same message to multiple systems at once (fan-out)»

    An SNS topic delivers a copy of every published message to all of its subscribers, so the producer publishes once and does not need to know each destination.

    When not: If the consumers must process at their own pace or may be down, SNS alone is not enough: combine it with one Amazon SQS queue per consumer. If the distribution depends on rules over the content of events from many sources (including SaaS), Amazon EventBridge is usually a better fit.

  • «publish/subscribe (pub/sub) model with push delivery»

    SNS pushes the message to subscribers as soon as it is published; nobody has to periodically check whether there are new messages.

    When not: If the scenario requires a single consumer to pull messages when it can (polling) and the messages to wait until they are processed, that is a queue: Amazon SQS. If you want routing rules based on an event pattern, look at Amazon EventBridge.

  • «notify administrators by email or SMS»

    A topic supports email and SMS subscriptions, and it is the usual target for operational alerts, for example when an alarm fires.

    When not: SNS sends notifications, not templated email campaigns or mailbox management; for marketing or transactional email at scale, the scenario points to another service. Also, the alarm itself is detected by Amazon CloudWatch: SNS only delivers it.

  • «each subscriber must receive only the messages it cares about»

    SNS lets you assign a filter policy to each subscription, so the subscriber receives only the messages whose attributes or body meet the conditions.

    When not: If filtering is the heart of the problem, with many rules over events from AWS services or SaaS applications and many types of targets, Amazon EventBridge may be the best option. If there is only one consumer, a topic is not needed.

  • «broadcast messages in order and without duplicates to multiple subscribers»

    SNS FIFO topics deliver messages in order and exactly once, and can feed the SQS FIFO queues of several systems.

    When not: With a single consumer, an SQS FIFO queue is enough. If the data will be analyzed as a continuous stream, Amazon Kinesis Data Streams is usually a better fit. A standard topic guarantees neither ordering nor the absence of duplicates. And if the distribution is decided with per-subscriber filters, the new Custom Event Bus in Amazon EventBridge also delivers in order per event group and deduplicates on publish.

  • «send push notifications to mobile applications»

    SNS Mobile Push delivers notifications to apps on mobile devices through push services such as APNs or FCM; they arrive as alerts, badges, or sounds.

    When not: If the scenario is about syncing app data or authenticating mobile users, push notification is not the core requirement and the answer will be another service.

Often paired with

  • Amazon SQS
  • AWS Lambda
Study Amazon SNS →