messaging

Design AWS messaging patterns with SQS, SNS, and EventBridge.

12|5|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/aws-samples/sample-claude-code-plugins-for-startups --skill messaging-aws-samples
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: messaging
Source: https://github.com/aws-samples/sample-claude-code-plugins-for-startups/tree/main/plugins/aws-dev-toolkit/skills/messaging
Command: npx skills add https://github.com/aws-samples/sample-claude-code-plugins-for-startups --skill messaging-aws-samples

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams design and implement reliable, scalable event-driven architectures using AWS messaging services such as SQS, SNS, and EventBridge.

Core Features & Use Cases

  • Guidance on when to use SQS, SNS, or EventBridge based on communication patterns (point-to-point, fan-out, event routing).
  • Best practices for reliability, including DLQs, retries, idempotency, and filtering.
  • Patterns for cross-account/cross-region events, event replay, and observability.

Quick Start

Design a basic, scalable event-driven messaging pattern using SQS, SNS, and EventBridge for a new microservices app.

Frequently Asked Questions about messaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I use SQS, SNS, or EventBridge for AWS messaging patterns?

Configure dead-letter queues in SQS and SNS to capture failed message deliveries after maximum retry limits. AWS messaging DLQ strategies ensure fault tolerance by isolating problematic events for debugging without blocking standard queue processing.

How do I design a fan-out architecture using SNS and SQS?

Subscribe multiple SQS queues to a single SNS topic to implement fan-out. This AWS messaging pattern allows one publisher to broadcast messages to multiple microservices concurrently, with each service processing its own queue independently.

Can EventBridge route events across different AWS accounts and regions?

EventBridge supports cross-account and cross-region event routing for distributed microservices. AWS messaging architectures use EventBridge rules to filter and forward events globally, enabling decoupled services to communicate securely across boundaries.

Why do I need idempotency and replay capabilities in event-driven AWS messaging?

Idempotency prevents duplicate processing when consumers retry messages, while replay allows reprocessing historical events during recovery. AWS messaging reliability relies on these patterns to maintain data consistency and recover gracefully from consumer failures.