What problem does it solve? Choosing between AWS messaging and streaming services is error-prone, and misconfigured queues, DLQs, and credentials cause silent message loss or security gaps. This Skill provides decision guidance and integration gotchas for SQS, SNS, EventBridge, Amazon MQ, Kinesis Data Streams, Data Firehose, Managed Service for Apache Flink, and Amazon MSK. ## Core Features & Use Cases - Pattern Selection: Distinguishes messaging (decoupled, consume-once) from streaming (durable, replayable) workloads and maps each to the right AWS service. - Service Comparison: Compares SQS, SNS, EventBridge, Amazon MQ, Kinesis Data Streams, Firehose, Flink, and MSK by differentiators like ordering, retention, and scaling units. - Integration Gotchas: Documents real pitfalls such as SQS system vs. user attributes, SNS-to-Firehose newline handling, DLQ queue policies, 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 recommendation for SNS with SQS subscriptions, plus the correct DLQ policy with aws:SourceArn conditions. ## Quick Start Ask which AWS service fits your workload, for example whether to use SQS or Kinesis for decoupling microservices with replay requirements.