AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with TypeScript/Python, API Gateway (REST/HTTP), DynamoDB, Step Functions,...
AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with TypeScript/Python, API Gateway (REST/HTTP), DynamoDB, Step Functions,...
This skill provides comprehensive guidance for building serverless applications and event-driven architectures on AWS based on Well-Architected Framework principles.
AWS Documentation Requirement
Always verify AWS facts using MCP tools (mcp__aws-mcp__* or mcp__*awsdocs*__*) before answering. The aws-mcp-setup dependency is auto-loaded — if MCP tools are unavailable, guide the user through that skill's setup flow.
Serverless MCP Servers
This skill leverages the CDK MCP server (provided via aws-cdk-development dependency) and AWS Documentation MCP for serverless guidance.
Note: The following AWS MCP servers are available separately via the Full AWS MCP Server (see aws-mcp-setup skill) and are not bundled with this plugin:
AWS Serverless MCP — SAM CLI lifecycle (init, deploy, local test)
AWS Lambda Tool MCP — Direct Lambda invocation
AWS Step Functions MCP — Workflow orchestration
Amazon SNS/SQS MCP — Messaging and queue management
When to Use This Skill
Use this skill when:
Building serverless applications with Lambda
Designing event-driven architectures
Implementing microservices patterns
Creating asynchronous processing workflows
Orchestrating multi-service transactions
Building real-time data processing pipelines
Implementing saga patterns for distributed transactions
Designing for scale and resilience
AWS Well-Architected Serverless Design Principles
1. Speedy, Simple, Singular
Functions should be concise and single-purpose
// ✅ GOOD - Single purpose, focused functionexportconstprocessOrder = async (event: OrderEvent) => {
// Only handles order processingconst order = awaitvalidateOrder(event);
awaitsaveOrder(order);
(order);
{ : , : .({ : order. }) };
};
= () => {
};
Important: When using CDK code examples from references, avoid hardcoding resource names (e.g., restApiName, eventBusName). Let CDK generate unique names automatically to enable reusability and parallel deployments. See aws-cdk-development skill for details.
Best Practices
Error Handling
Implement comprehensive error handling:
exportconsthandler = async (event: SQSEvent) => {
constfailures: SQSBatchItemFailure[] = [];
for (const record of event.Records) {
try {
awaitprocessRecord(record);
} catch (error) {
console.error('Failed to process record:', record.messageId, error);
failures.push({ itemIdentifier: record.messageId });
}
}
// Return partial batch failures for retryreturn { batchItemFailures: failures };
};
Use the CDK MCP server (via aws-cdk-development dependency) for construct recommendations and CDK-specific guidance when building serverless infrastructure.
Use AWS Documentation MCP to verify service features, regional availability, and API specifications before implementing.
Additional Resources
This skill includes comprehensive reference documentation based on AWS best practices: