Microsoft Azure → Amazon Web Services
AWS equivalent of Azure Event Grid
The closest AWS equivalents of Azure Event Grid are Amazon EventBridge (event buses & Pipes) and Amazon SNS.
About Azure Event Grid
| Provider | Microsoft Azure |
|---|---|
| Status | Generally available |
| What it is | Managed pub/sub event routing. System topics for Azure events, custom topics and namespaces, CloudEvents, push and pull delivery, and an MQTT broker (v3.1.1 and v5). |
| Documentation | learn.microsoft.com |
| Pricing | Official pricing page |
AWS mappings (2)
| Capability | AWS equivalent | Match |
|---|---|---|
| Event bus and event routing | Amazon EventBridge (event buses & Pipes) | Partial match |
| Pub/sub fan-out and notifications | Amazon SNS | Partial match |
Events, queues & pub/sub(2)
Event bus and event routing Partial match
Amazon EventBridge maps to Azure Event Grid. Both are serverless event routers with filtering and native cloud-service events, but they differ in schema, delivery modes, and extras such as archive and replay (EventBridge) or MQTT (Event Grid).
- Sources. EventBridge gets AWS service events on the default bus, SaaS partner event sources, and custom buses. Event Grid gets Azure resource events on system topics, plus custom topics and namespaces. Partner events are also supported.
- Format. EventBridge uses its own event envelope with JSON pattern matching. Event Grid supports CloudEvents 1.0 (recommended) and the Event Grid schema, with advanced filters.
- Delivery. EventBridge pushes to targets (Lambda, SQS, Step Functions, API destinations) and supports archive and replay. Event Grid namespaces add pull delivery and an MQTT broker. Push delivery has retries and dead-lettering.
Pub/sub fan-out and notifications Partial match
Amazon SNS maps to Azure Service Bus topics (durable fan-out to subscriptions) and Azure Event Grid (push to webhooks and services). For SMS, email, and mobile push, Azure uses Azure Communication Services and Notification Hubs, which aren't mapped here.
- SNS combines app-to-app fan-out (to SQS, Lambda, HTTP, Firehose) and app-to-person delivery (SMS, email, mobile push) in one service. Azure splits these across Service Bus topics or Event Grid (A2A) and Communication Services or Notification Hubs (A2P).
- Filtering. SNS uses subscription filter policies on attributes or the body. Service Bus subscriptions use SQL or correlation filters. Event Grid has subject and advanced filters.
- FIFO. SNS FIFO topics pair with SQS FIFO queues. Service Bus sessions on topic subscriptions provide ordering.