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 patterns, 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 (decoupled, consumed-once) and streaming (durable, 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. - Customer Communication Routing: Identifies which AWS service owns each application-to-person channel (Amazon SES for email, End User Messaging for SMS/WhatsApp/voice/push) and defers to the specialized skill. - Integration Gotchas: Documents common pitfalls such as SQS system vs. user message attributes, SNS-to-Firehose newline handling, DLQ queue policies, and Secrets Manager credential requirements. - Use Case: When designing an event-driven architecture, ask which service fits a fan-out notification workload and receive a grounded recommendation with integration caveats. ## Quick Start Ask which AWS service to use for decoupling microservices with a task queue and how it differs from Kinesis streaming.