What problem does it solve? Choosing between AWS messaging and streaming services is confusing because SQS, SNS, EventBridge, Amazon MQ, Kinesis Data Streams, Data Firehose, Managed Service for Apache Flink, and MSK overlap in capability. This Skill explains the messaging versus streaming distinction, maps workloads to the right service, and routes customer communication questions (email, SMS, WhatsApp, voice, push) to the correct specialized skill. ## Core Features & Use Cases - Pattern Selection: Explains the differences between messaging (consumed once, no replay) and streaming (retained, replayable, ordered) so you can match the pattern to your workload. - Service Comparison Tables: Compares SQS, SNS, EventBridge, Amazon MQ, Kinesis Data Streams, Data Firehose, Managed Flink, and MSK by best-fit use case and key differentiator. - Integration Gotchas: Documents real pitfalls such as SQS system vs. user message attributes, SNS-to-Firehose newline handling, DLQ queue policies for EventBridge and SNS, and Secrets Manager requirements for MSK SASL/SCRAM. - Use Case: When designing an event-driven architecture, ask which service fits a fan-out notification workload and get a grounded recommendation plus the DLQ and IAM policy configuration needed to make it work. ## Quick Start Ask which AWS service to use for decoupling microservices with a task queue and how to configure its dead-letter queue securely.