/aws-lambda

name: aws-lambda
description: "Design, build, deploy, test, and debug serverless applications with AWS Lambda. Triggers on phrases like: Lambda function, event source, serverless application, API Gateway, EventBridge, Step Functions, serverless API, event-driven architecture, Lambda trigger. For deploying non-serverless apps to AWS, use deploy-on-aws plugin instead."
argument-hint: "[what are you building?]"

AWS Lambda Serverless Development

Design, build, deploy, and debug serverless applications with AWS serverless services. This skill provides access to serverless development guidance through the AWS Serverless MCP Server, helping you to build production-ready serverless applications with best practices built-in.

Use SAM CLI for project initialization and deployment, Lambda Web Adapter for web applications, or Event Source Mappings for event-driven architectures. AWS handles infrastructure provisioning, scaling, and monitoring automatically.

**Key capabilities:**

• **SAM CLI Integration**: Initialize, build, deploy, and test serverless applications
• **Web Application Deployment**: Deploy full-stack applications with Lambda Web Adapter
• **Event Source Mappings**: Configure Lambda triggers for DynamoDB, Kinesis, SQS, Kafka
• **Lambda durable functions**: Resilient multi-step applications with checkpointing — see the [durable-functions skill](../aws-lambda-durable-functions/) for guidance
• **Lambda Managed Instances**: Run Lambda on dedicated EC2 instances with managed lifecycle — see the [managed-instances skill](../aws-lambda-managed-instances/) for evaluation, configuration, and migration guidance
• **Schema Management**: Type-safe EventBridge integration with schema registry
• **Observability**: CloudWatch logs, metrics, and X-Ray tracing
• **Performance Optimization**: Right-sizing, cost optimization, and troubleshooting

When to Load Reference Files

Load the appropriate reference file based on what the user is working on:

• **Getting started**, **what to build**, **project type decision**, or **working with existing projects** -> see [references/getting-started.md](references/getting-started.md)
• **SAM**, **CDK**, **deployment**, **IaC templates**, **CDK constructs**, or **CI/CD pipelines** -> see the [aws-serverless-deployment skill](../aws-serverless-deployment/) (separate skill in this plugin)
• **Web app deployment**, **Lambda Web Adapter**, **API endpoints**, **CORS**, **authentication**, **custom domains**, or **sam local start-api** -> see [references/web-app-deployment.md](references/web-app-deployment.md)
• **Event sources**, **DynamoDB Streams**, **Kinesis**, **SQS**, **Kafka**, **S3 notifications**, or **SNS** -> see [references/event-sources.md](references/event-sources.md)
• **EventBridge**, **event bus**, **event patterns**, **event design**, **Pipes**, or **schema registry** -> see [references/event-driven-architecture.md](references/event-driven-architecture.md)
• **Durable functions**, **checkpointing**, **replay model**, **saga pattern**, or **long-running Lambda workflows** -> see the [durable-functions skill](../aws-lambda-durable-functions/) (separate skill in this plugin with full SDK reference, testing, and deployment guides)
• **Lambda Managed Instances**, **LMI**, **capacity providers**, **multi-concurrency**, **EC2-backed Lambda**, **cold start elimination**, or **Lambda cost optimization with Reserved Instances** -> see the [managed-instances skill](../aws-lambda-managed-instances/) (separate skill in this plugin for evaluation, configuration, and migration)
• **Orchestration**, **workflows**, or **Durable Functions vs Step Functions** -> see [references/orchestration-and-workflows.md](references/orchestration-and-workflows.md)
• **Step Functions**, **ASL**, **state machines**, **JSONata**, **Distributed Map**, **SDK integrations**, **TestState API**, **mocking service integrations**, or **state machine unit tests** -> see the [aws-step-functions skill](../aws-step-functions/) for comprehensive guidance
• **Observability**, **logging**, **tracing**, **metrics**, **alarms**, or **dashboards** -> see [references/observability.md](references/observability.md)
• **Optimization**, **cold starts**, **memory tuning**, **cost**, or **streaming** -> see [references/optimization.md](references/optimization.md)
• **Powertools**, **idempotency**, **feature flags**, **parameters**, **parser**, **batch processing**, or **data masking** -> see [references/powertools.md](references/powertools.md)
• **Troubleshooting**, **errors**, **debugging**, or **deployment failures** -> see [references/troubleshooting.md](references/troubleshooting.md)

Best Practices

Project Setup

• Do: Use `sam_init` or `cdk init` with an appropriate template for your use case
• Do: Set global defaults for timeout, memory, runtime, and tracing (`Globals` in SAM, construct props in CDK)
• Do: Use AWS Lambda Powertools for structured logging, tracing, metrics (EMF), idempotency, and batch processing — available for Python, TypeScript, Java, and .NET
• Don't: Copy-paste templates from the internet without understanding the resource configuration
• Don't: Use the same memory and timeout values for all functions regardless of workload

Security

• Do: Follow least-privilege IAM policies scoped to specific resources and actions
• Do: Use `secure_esm_*` tools to generate correct IAM policies for event source mappings
• Do: Store secrets in AWS Secrets Manager or SSM Parameter Store, never in environment variables
• Do: Use VPC endpoints instead of NAT Gateways for AWS service access when possible
• Do: Enable Amazon GuardDuty Lambda Protection to monitor function network activity for threats (cryptocurrency mining, data exfiltration, C2 callbacks)
• Don't: Use wildcard (`*`) resource ARNs or actions in IAM policies
• Don't: Hardcode credentials or secrets in application code or templates
• Don't: Store user data or sensitive information in module-level variables — exe