Microsoft Azure → Amazon Web Services
AWS equivalent of Azure Service Bus
The closest AWS equivalents of Azure Service Bus are Amazon SQS, Amazon SNS and Amazon MQ.
About Azure Service Bus
| Provider | Microsoft Azure |
|---|---|
| Status | Generally available |
| What it is | Enterprise message broker with queues and topics/subscriptions. Supports sessions (FIFO), duplicate detection, transactions, dead-lettering, scheduled messages, AMQP 1.0, and JMS 2.0 (Premium). |
| Documentation | learn.microsoft.com |
| Pricing | Official pricing page |
AWS mappings (3)
| Capability | AWS equivalent | Match |
|---|---|---|
| Message queues | Amazon SQS | Direct match |
| Pub/sub fan-out and notifications | Amazon SNS | Partial match |
| Managed open-source message brokers (ActiveMQ, RabbitMQ) | Amazon MQ | Partial match |
Events, queues & pub/sub(3)
Message queues Direct match
Amazon SQS maps to Azure Service Bus queues (feature parity, including FIFO via sessions) or Azure Queue Storage (simple, cheap queues).
- Ordering. SQS FIFO queues order messages per message group ID with exactly-once processing. Service Bus uses sessions for ordered, grouped processing and duplicate detection. Queue Storage has no ordering guarantees.
- Features. Service Bus adds transactions, scheduled delivery, deferral, auto-forwarding, and AMQP 1.0. SQS adds long polling, delay queues, and a visibility timeout. Both have dead-letter queues.
- Limits. SQS messages can be up to 1 MiB (larger with the extended client library and S3). Queue Storage messages are up to 64 KB. Service Bus allows 256 KB on Standard and up to 100 MB on Premium.
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.
Managed open-source message brokers (ActiveMQ, RabbitMQ) Partial match
Azure has no managed ActiveMQ or RabbitMQ service like Amazon MQ. The nearest first-party target is Azure Service Bus Premium (AMQP 1.0 and JMS 2.0); otherwise use Marketplace or self-managed brokers.
- Amazon MQ runs the actual open-source broker engines, so existing clients and protocols work unchanged. Service Bus is a different broker with its own semantics, and RabbitMQ (AMQP 0-9-1) clients need code changes.
- JMS. Service Bus Premium supports JMS 2.0 over AMQP 1.0, which covers many ActiveMQ/JMS migrations.
- MQTT. Event Grid namespaces include an MQTT broker (v3.1.1 and v5), an option for IoT-style MQTT clients.