aws-serverless-eda

Designs AWS serverless and event-driven architectures using Lambda, API Gateway, Step Functions, and EventBridge.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/farslab/claude-skills --skill aws-serverless-eda-farslab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-serverless-eda
Source: https://github.com/farslab/claude-skills/tree/main/aws-serverless-eda
Command: npx skills add https://github.com/farslab/claude-skills --skill aws-serverless-eda-farslab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building serverless applications on AWS requires navigating dozens of services, patterns, and Well-Architected best practices, and mistakes in areas like idempotency, error handling, or orchestration lead to fragile, costly systems. ## Core Features & Use Cases - Well-Architected Serverless Guidance: Applies the seven serverless design principles (single-purpose functions, share nothing, state machine orchestration, event-driven triggers, idempotency) with TypeScript and Python code examples. - Architecture Pattern Library: Provides reference implementations for EventBridge routing, SQS queue processing, SNS fan-out, Step Functions sagas, event sourcing with DynamoDB Streams, and API-driven microservices. - Operational Best Practices: Covers security (IAM least privilege, encryption), observability (X-Ray tracing, structured logging, CloudWatch alarms), performance tuning (cold starts, memory sizing, provisioned concurrency), and deployment strategies (canary, blue/green, CI/CD pipelines). - Use Case: When asked to build an order-processing backend, it guides you to expose an API Gateway REST endpoint backed by Lambda, publish OrderPlaced events to EventBridge, orchestrate payment and fulfillment with a Step Functions saga, and configure DLQs with alarms for failure handling. ## Quick Start Ask the assistant to design a serverless order-processing API on AWS with Lambda, DynamoDB, and event-driven async workflows following Well-Architected best practices.

Frequently Asked Questions about aws-serverless-eda

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

FAQPage Schema
How do I build a serverless REST API with AWS Lambda and API Gateway?▼

Create an API Gateway REST or HTTP API backed by Lambda functions using CDK or SAM, with each function handling a single responsibility. The skill provides TypeScript examples for API-driven microservices, including DynamoDB integration, IAM least-privilege grants, and X-Ray tracing.

Should I use Step Functions or Lambda function chaining for workflows?▼

Use Step Functions for orchestration instead of chaining Lambda invocations directly. State machines provide visual workflows, built-in retries and error handling, execution history, and service integrations without code, making complex flows easier to debug and maintain.

How do I make SQS Lambda consumers idempotent?▼

Track processed message IDs in DynamoDB with a conditional write that fails on duplicates, and return partial batch failures so only failed records are retried. The skill includes complete idempotency handler examples with TTL-based cleanup of processed records.

What is the difference between SQS, SNS, and EventBridge for events?▼

SQS provides point-to-point queueing with consumer-controlled polling, SNS enables pub/sub fan-out to multiple subscribers, and EventBridge offers content-based event routing with schema registries and cross-account delivery. The skill's EDA patterns reference covers when to combine them, such as SNS-to-SQS fan-out.

How do I reduce Lambda cold start latency?▼

Minimize deployment package size with tree-shaking and minification, initialize SDK clients outside the handler, and use provisioned concurrency for latency-sensitive paths. Java functions can use SnapStart for up to 10x faster cold starts, and Graviton2 ARM64 improves price-performance.

When should I use canary deployments for Lambda functions?▼

Use canary or linear deployment preferences for production Lambda updates to shift traffic gradually while CloudWatch alarms monitor errors and latency. CodeDeploy automatically rolls back if alarms trigger, and pre/post-traffic hooks validate the new version before full rollout.