aws-architecture-patterns

Design AWS serverless architectures with API Gateway, Lambda, SQS, EventBridge, Step Functions, and DynamoDB.

6|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/wesleyosantos91/multi-agents --skill aws-architecture-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-architecture-patterns
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/aws-architecture-patterns
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill aws-architecture-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you choose and implement correct AWS architecture patterns so you can build reliable serverless systems without ad-hoc, brittle service wiring.

Core Features & Use Cases

  • Serverless API pattern (API Gateway + Lambda + DynamoDB): Use for request/response workloads with variable traffic.
  • Async processing (SQS + Lambda + DLQ + batch failure reporting): Use for decoupled, retryable workflows when latency is not critical.
  • Event-driven orchestration (EventBridge + Rules + Lambdas): Use for routing multiple consumers based on event source and detail.
  • Workflow orchestration (Step Functions): Use for multi-step flows with decisions and compensation (saga-style) and long timeouts.
  • Data modeling guidance (DynamoDB single-table design): Use to structure PK/SK and GSIs to avoid scans and support access patterns.
  • Performance and cost considerations (cold start mitigation, Lambda Layers, caching, ECS/Fargate selection): Use to reduce latency risk and pick the right compute service.

Quick Start

Ask it to propose the best AWS architecture for a new order processing system (API + async events + retries), including the exact services, decision points, and key IaC snippets for your chosen stack.

Frequently Asked Questions about aws-architecture-patterns

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

FAQPage Schema
How do I design an AWS serverless architecture for an order processing system with APIs and async retries?

Use DynamoDB single-table design to structure partition and sort keys alongside GSIs, ensuring your data model directly supports specific application access patterns. This approach prevents expensive table scans and optimizes query performance for serverless workloads.

What is the best way to route events to multiple consumers in an event-driven AWS architecture?

Event-driven routing is best handled using EventBridge with rules to filter and route events to different Lambda functions based on event source and detail. This fan-out pattern decouples producers from consumers, allowing reliable independent processing.

When should I use Step Functions instead of SQS and Lambda for AWS workflow orchestration?

Use Step Functions for AWS workflow orchestration when your multi-step flow requires decisions, compensation logic like saga patterns, or long timeouts. SQS and Lambda are better suited for decoupled, independent async processing where latency is not critical.

How do I mitigate Lambda cold start performance issues in a serverless API pattern?

Mitigate Lambda cold start issues by applying performance considerations like using Lambda Layers to optimize deployment packages and implementing caching strategies. You can also evaluate whether ECS or Fargate is a more appropriate compute service for your workload.

Can I use this Skill to generate Terraform IaC snippets for my chosen AWS architecture pattern?

Yes, you can request the exact AWS services, decision points, and key IaC snippets for your chosen stack, including Terraform implementation details. This helps transition directly from architecture pattern selection to infrastructure provisioning.