/aws-messaging-and-streaming

name: aws-messaging-and-streaming
description: >-
  Guides general use of AWS messaging and streaming services. Covers Amazon SQS,
  Amazon SNS, Amazon EventBridge, Amazon MQ, Amazon Kinesis Data Streams,
  Amazon Data Firehose, Amazon Managed Service for Apache Flink, and Amazon Managed Streaming for Apache Kafka (MSK).
  Use when reasoning about messaging and streaming patterns.
  Also identifies which AWS service owns each customer communication channel:
  email (Amazon SES), and WhatsApp, SMS, MMS, RCS, voice and mobile push
  (the AWS End User Messaging family of services).
  Routes the request to the specialized skill for that channel.
  Defers to the channel's specialized skill when the user already named a specific channel.
  In general, use specific skills or documentation searches for detailed service-specific questions.
  Do NOT use for MSK or Managed Service for Apache Flink questions, prefer specific skills.
  Does not configure customer communication channels; defers to specific skills.
metadata:
  version: "4"

AWS Messaging & Streaming Services

When answering AWS messaging and streaming questions, verify specific numbers, versions, limits, and behavioral details from service-specific skills or official AWS documentation. When uncertain, search skills or docs rather than guessing. Fabricated configuration options or incorrect version numbers are worse than admitting uncertainty.

When a question asks about recommended configurations (CloudWatch alarm settings, thresholds, missing data treatment), search for the service-specific skills or documentation rather than relying on general best practices.

Overview

Domain expertise for choosing and using AWS services that move data between producers and consumers. This skill covers two fundamental patterns — **messaging** and **streaming** — and the AWS services that implement each. It also marks the boundary with **customer communication** — messages delivered to people rather than to application components — and routes those questions to the skill or AWS documentation that owns each channel (see Customer Communications (Application-to-Person)). Use this skill to decide which pattern fits a workload, select the right service, and understand how services integrate with each other.

For specific guidance on individual AWS services, see reference files or service-specific Skills.

Streaming and Messaging

What Is Messaging?

Messaging enables **decoupled, asynchronous communication** between components. A producer sends a message; one or more consumers receive and process it. Once processed, the message is typically deleted. Messaging services handle delivery guarantees, retries, and dead-letter routing.

**Key characteristics:**

• Messages are consumed once (point-to-point) or fanned out (pub/sub), then removed
• No replay — once acknowledged, a message is gone
• Designed for command/request workloads, task distribution, and event notification

What Is Streaming?

Streaming enables **ordered, durable, high-throughput continuous data flow**. Producers append records to a log; consumers read from positions in that log. Records persist for a configurable retention period regardless of consumption.

**Key characteristics:**

• Records are retained and replayable within the retention window
• Strict ordering within a partition/shard
• Multiple independent consumers can read the same data at different positions
• Designed for event sourcing, real-time analytics, change data capture, and continuous processing

Key Differences

| Dimension | Messaging | Streaming | |---|---|---| | **Data lifecycle** | Deleted after consumption | Retained for replay (hours to indefinitely) | | **Ordering** | Best-effort (Standard) or per-group (FIFO) | Strict per-partition/shard | | **Consumer model** | Competing consumers (work distribution) | Independent readers (fan-out by position) | | **Throughput pattern** | Bursty, variable | Sustained, high-volume | | **Replay** | Not supported (except DLQ redrive) | Native — seek to any position in retention | | **Typical latency** | Milliseconds (push or short-poll) | Milliseconds to low seconds | | **Scaling unit** | Concurrency (consumers/pollers) | Partitions or shards |

Messaging Use Cases

• Decoupling microservices with request/response or command patterns
• Distributing work across a pool of competing consumers (task queues)
• Fan-out notifications where each subscriber acts independently
• Workloads that are bursty and benefit from queue buffering
• Migrating existing JMS/AMQP applications (Amazon MQ)

Streaming Use Cases

• Continuous, high-throughput data ingestion (logs, metrics, clickstreams, IoT telemetry)
• Event sourcing where consumers need to replay from any point in time
• Multiple independent consumers processing the same data differently
• Real-time analytics, windowed aggregations, or complex event processing
• Change data capture (CDC) pipelines

Messaging Services

These services are generally used for messaging workloads. Sometimes streaming services (Kinesis Data Streams, Managed Streaming for Apache Kafka) are also used for messaging workloads, depending on exact use case and requirements.

| Service | Best For | Key Differentiator | |---|---|---| | **Amazon SQS** | Task queues, decoupling, buffering | Fully managed, unlimited throughput (Standard), exactly-once (FIFO), fair queues for multi-tenant workloads | | **Amazon SNS** | Fan-out, pub/sub notifications | Push to multiple subscribers (SQS, Lambda, HTTP; email/SMS endpoints suit operational alerts — for customer email or SMS see Customer Communications (Application-to-Person)) | | **Amazon EventBridge** | Event routing, cross-account/SaaS integration | Content-based filtering, schema registry, 200+ AWS source integrations | | **Amazon MQ** | Lift-and-shift of existing JMS/AMQP/MQTT apps | Protocol compatibility (ActiveMQ, RabbitMQ) for legacy migration |

Streaming Services

These servi