Concevez, développez, déployez, testez et déboguez des applications serverless en utilisant AWS Lambda et les services serverless associés.
- Étoiles GitHub
- 938
- Fichiers
- 10
- Dernier commit
- 10 nov. 2026
- Licence
- Apache-2.0
- Outils autorisés
- —
Que fait la skill aws-lambda ?
Concevez, développez, déployez, testez et déboguez des applications serverless en utilisant AWS Lambda et les services serverless associés.
Résumé généré à partir du SKILL.md de la skill.
À propos du skill aws-lambda
La fonction principale de ce SKILL est de permettre la construction et la gestion d'applications serverless sur AWS. Il aide les développeurs à concevoir, déployer, tester et déboguer des fonctions Lambda ainsi que les services associés tels qu'API Gateway, EventBridge et Step Functions. Ce SKILL fournit des conseils pour créer des architectures prêtes pour la production, incluant des systèmes pilotés par les événements et des applications web utilisant le Lambda Web Adapter.
Un agent doit charger ce SKILL lorsqu'un utilisateur a besoin d'initialiser des projets avec SAM CLI ou CDK, de configurer des mappings de sources d'événements pour des services comme DynamoDB ou SQS, ou d'optimiser les performances via l'ajustement de la mémoire et la réduction des cold starts. Il s'appuie sur l'AWS Serverless MCP Server pour fournir des conseils techniques et des bonnes pratiques. Le SKILL génère de l'infrastructure as code, des commandes de déploiement et des étapes de dépannage basées sur le composant serverless spécifique en cours de développement.
Cet outil se distingue en offrant un support spécialisé pour des patterns complexes tels que les fonctions durables et les instances managées. Il inclut également un hook de validation automatique qui exécute SAM validate après chaque modification de template afin de garantir l'exactitude de la configuration.
Ce qu'un agent peut faire avec
- 1Initialiser un nouveau projet serverlessCréez une nouvelle application serverless en utilisant des templates SAM CLI ou CDK.
- 2Déployer une application webConfigurez une application web full-stack en utilisant le Lambda Web Adapter.
- 3Configurer des déclencheurs d'événementsConfigurez des mappings de sources d'événements pour des services tels que DynamoDB, Kinesis ou SQS.
Rédigé à partir du SKILL.md du skill. Chaque cas d'utilisation est vérifié par rapport à une citation de celui-ci.
Comment installer la skill aws-lambda
Chaque commande copie le dossier de la skill dans le répertoire des skills du client. Redémarrez le client ou démarrez une nouvelle session pour la charger.Installer la skill aws-lambda dans Plugin
/plugin marketplace add awslabs/agent-plugins /plugin install aws-serverless@agent-plugins-for-aws
Installer la skill aws-lambda dans Claude Code
~/.claude/skills/aws-lambda/SKILL.md
$ npx degit awslabs/agent-plugins/plugins/aws-serverless/skills/aws-lambda ~/.claude/skills/aws-lambdaInstaller la skill aws-lambda dans Claude Code (project)
.claude/skills/aws-lambda/SKILL.md
$ npx degit awslabs/agent-plugins/plugins/aws-serverless/skills/aws-lambda .claude/skills/aws-lambdaInstaller la skill aws-lambda dans Codex
~/.agents/skills/aws-lambda/SKILL.md
$ npx degit awslabs/agent-plugins/plugins/aws-serverless/skills/aws-lambda ~/.agents/skills/aws-lambdaInstaller la skill aws-lambda dans Gemini CLI
~/.gemini/skills/aws-lambda/SKILL.md
$ npx degit awslabs/agent-plugins/plugins/aws-serverless/skills/aws-lambda ~/.gemini/skills/aws-lambdaInstaller la skill aws-lambda dans Claude.ai
npx degit awslabs/agent-plugins/plugins/aws-serverless/skills/aws-lambda aws-lambda && zip -r aws-lambda.zip aws-lambda # claude.ai → Customize → Skills → + → Create skill → Upload a skill → aws-lambda.zip
Vérifications automatisées
Exécuté le 15 nov. 2026Rapport complet →A réussi nos vérifications automatiques. Ce n'est pas un audit de sécurité : lisez les scripts avant de laisser un agent les exécuter. Fonctionnement des vérifications
- Dépôt source lié et accessibleawslabs/agent-plugins/plugins/aws-serverless/skills/aws-lambda is public and reachablegithub.com/awslabs/agent-plugins/tree/HEAD/plugins/aws-serve ↗Réussi
- Licence open source (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit 2026-11-10github.com/awslabs/agent-plugins/commits ↗Réussi
- Aucun téléchargement-exécution ni vol d'identifiants dans les scriptsNo scripts in the skill folderRéussi
- Aucune instruction cachée dans SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/awslabs/agent-plugins/blob/HEAD/plugins/aws-serve ↗Réussi
- Les outils préautorisés sont limitésNo pre-approved tools; the agent asks before using onegithub.com/awslabs/agent-plugins/blob/HEAD/plugins/aws-serve ↗Réussi
- SKILL.md respecte le format Agent SkillsValid name and description; says when to use it; 173 linesgithub.com/awslabs/agent-plugins/blob/HEAD/plugins/aws-serve ↗Réussi
SKILL.md
Voir sur GitHubAWS 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 for guidance
- Lambda Managed Instances: Run Lambda on dedicated EC2 instances with managed lifecycle — see the managed-instances skill 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
- SAM, CDK, deployment, IaC templates, CDK constructs, or CI/CD pipelines -> see the aws-serverless-deployment skill (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
- Event sources, DynamoDB Streams, Kinesis, SQS, Kafka, S3 notifications, or SNS -> see references/event-sources.md
- EventBridge, event bus, event patterns, event design, Pipes, or schema registry -> see references/event-driven-architecture.md
- Durable functions, checkpointing, replay model, saga pattern, or long-running Lambda workflows -> see the durable-functions skill (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 (separate skill in this plugin for evaluation, configuration, and migration)
- Orchestration, workflows, or Durable Functions vs Step Functions -> see 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 for comprehensive guidance
- Observability, logging, tracing, metrics, alarms, or dashboards -> see references/observability.md
- Optimization, cold starts, memory tuning, cost, or streaming -> see references/optimization.md
- Powertools, idempotency, feature flags, parameters, parser, batch processing, or data masking -> see references/powertools.md
- Troubleshooting, errors, debugging, or deployment failures -> see references/troubleshooting.md
Best Practices
Project Setup
- Do: Use
sam_initorcdk initwith an appropriate template for your use case - Do: Set global defaults for timeout, memory, runtime, and tracing (
Globalsin 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 — execution environments can be reused across different callers
Idempotency
- Do: Write idempotent function code — Lambda delivers events at least once, so duplicate invocations must be safe
- Do: Use the AWS Lambda Powertools Idempotency utility (backed by DynamoDB) for critical operations
- Do: Validate and deduplicate events at the start of the handler before performing side effects
- Don't: Assume an event will only ever be processed once
For topic-specific best practices, see the dedicated guide files in the reference table above.
Lambda Limits Quick Reference
Limits that developers commonly hit:
| Resource | Limit |
|---|---|
| Function timeout | 900 seconds (15 minutes) |
| Memory | 128 MB – 10,240 MB |
| 1 vCPU equivalent | 1,769 MB memory |
| Synchronous payload (request + response) | 6 MB each |
| Async invocation payload | 1 MB |
| Streamed response | 200 MB |
| Deployment package (.zip, uncompressed) | 250 MB |
| Deployment package (.zip upload, compressed) | 50 MB |
| Container image | 10 GB |
| Layers per function | 5 |
| Environment variables (aggregate) | 4 KB |
/tmp ephemeral storage |
512 MB – 10,240 MB |
| Account concurrent executions (default) | 1,000 (requestable increase) |
| Burst scaling rate | 1,000 new executions per 10 seconds |
Check Service Quotas for your account limits: aws lambda get-account-settings
Troubleshooting Quick Reference
| Error | Cause | Solution |
|---|---|---|
Build Failed |
Missing dependencies | Run sam_build with use_container: true |
Stack is in ROLLBACK_COMPLETE |
Previous deploy failed | Delete stack with aws cloudformation delete-stack, redeploy |
IteratorAge increasing |
Stream consumer falling behind | Increase ParallelizationFactor and BatchSize. Use esm_optimize |
| EventBridge events silently dropped | No DLQ, retries exhausted | Add RetryPolicy + DeadLetterConfig to rule target |
| Step Functions failing silently | No retry on Task state | Add Retry with Lambda.ServiceException, Lambda.AWSLambdaException |
| Durable Function not resuming | Missing IAM permissions | Add lambda:CheckpointDurableExecution and lambda:GetDurableExecutionState — see durable-functions skill |
For detailed troubleshooting, see references/troubleshooting.md.
Configuration
AWS CLI Setup
This skill requires that AWS credentials are configured on the host machine:
Verify access: Run aws sts get-caller-identity to confirm credentials are valid
SAM CLI Setup
- Install SAM CLI: Follow the SAM CLI installation guide
- Verify: Run
sam --version
Container Runtime Setup
- Install a Docker compatible container runtime: Required for
sam_local_invokeand container-based builds - Verify: Use an appropriate command such as
docker --versionorfinch --version
MCP Server Configuration
Write access is enabled by default. The plugin ships with --allow-write in .mcp.json, so the MCP server can create projects, generate IaC, and deploy on behalf of the user.
Access to sensitive data (like Lambda and API Gateway logs) is not enabled by default. To grant it, add --allow-sensitive-data-access to .mcp.json.
SAM Template Validation Hook
This plugin includes a PostToolUse hook that runs sam validate automatically after any edit to template.yaml or template.yml. If validation fails, the error is returned as a system message so you can fix it immediately. The hook requires SAM CLI and jq to be installed; if either is missing, validation is skipped with a system message. Users can disable it via /hooks.
Verify: Run jq --version
Language selection
Default: TypeScript
Override syntax:
- "use Python" → Generate Python code
- "use JavaScript" → Generate JavaScript code
When not specified, ALWAYS use TypeScript
IaC framework selection
Default: CDK
Override syntax:
- "use CloudFormation" → Generate YAML templates
- "use SAM" → Generate YAML templates
When not specified, ALWAYS use CDK
Serverless MCP Server Unavailable
- Inform user: "AWS Serverless MCP not responding"
- Ask: "Proceed without MCP support?"
- DO NOT continue without user confirmation
Resources
Fichiers de cette skill
10Questions sur la skill aws-lambda
Comment installer la skill aws-lambda dans Claude Code ?
Exécutez npx degit awslabs/agent-plugins/plugins/aws-serverless/skills/aws-lambda ~/.claude/skills/aws-lambda. Claude Code charge les skills depuis ~/.claude/skills (tous les projets) ou .claude/skills (un seul projet) et utilise une skill lorsque sa description correspond à la tâche.
Quels clients peuvent utiliser la skill aws-lambda ?
Tout client qui lit le format Agent Skills : Claude Code, Codex, Gemini CLI et claude.ai (envoi sous forme de ZIP). Les scripts de la skill ne s'exécutent que si le client autorise l'exécution de code.
Quel est le timeout maximum d'une fonction AWS Lambda ?
Le timeout maximum d'une fonction est de 900 secondes, soit 15 minutes.
Comment dois-je gérer les secrets dans mes fonctions Lambda ?
Vous devriez stocker vos secrets dans AWS Secrets Manager ou SSM Parameter Store plutôt que d'utiliser des variables d'environnement.
Que dois-je faire si mon build échoue à cause de dépendances manquantes ?
Vous devez exécuter sam_build avec le flag use_container: true.
Est-il sûr de supposer qu'un événement ne sera traité qu'une seule fois ?
Non, vous devez écrire un code de fonction idempotent car Lambda délivre les événements au moins une fois, ce qui signifie que les invocations en double doivent être gérées en toute sécurité.