
AWS Serverless Deployment
AWS SAM and AWS CDK deployment for serverless applications.
Install
npx skills add awslabs/agent-plugins --skill aws-serverless-deployment -g -a claude-code -y- Repository
- awslabs/agent-plugins933
- Category
- DevOps
- Updated
- 20d ago
- License
- Apache-2.0
- Context cost
- Lightabout 1,228 tokens
- Runs scripts
- No, instructions only
What it does
AWS SAM and AWS CDK deployment for serverless applications. Triggers on phrases like: use SAM, SAM template, SAM init, SAM deploy, CDK serverless, CDK Lambda construct, NodejsFunction, PythonFunction, SAM and CDK together, serverless CI/CD pipeline. For general app deployment with service selection, use deploy-on-aws plugin instead.
AWS Serverless Deployment
Deploy serverless applications to AWS using SAM or CDK. This skill covers project scaffolding, IaC templates, CDK constructs and patterns, deployment workflows, CI/CD pipelines, and SAM/CDK coexistence.
For Lambda runtime behavior, event sources, orchestration, observability, and optimization, see the aws-lambda skill.
When to Load Reference Files
Load the appropriate reference file based on what the user is working on:
- SAM project setup, templates, deployment workflow, local testing, or container images -> see references/sam-project-setup.md
- CDK project setup, constructs, CDK testing, or CDK pipelines -> see references/cdk-project-setup.md
- CDK Lambda constructs, NodejsFunction, PythonFunction, or CDK Function -> see references/cdk-lambda-constructs.md
- CDK serverless patterns, API Gateway CDK, Function URL CDK, EventBridge CDK, DynamoDB CDK, or SQS CDK -> see references/cdk-serverless-patterns.md
- SAM and CDK coexistence, migrating from SAM to CDK, or using sam build with CDK -> see references/sam-cdk-coexistence.md
Best Practices
SAM
- Do: Use
sam_initwith an appropriate template for your use case - Do: Set global defaults for timeout, memory, runtime, and tracing in the
Globalssection - Do: Use
samconfig.tomlenvironment-specific sections for multi-environment deployments - Do: Use
sam build --use-containerwhen native dependencies are involved - Don't: Copy-paste templates from the internet without understanding the resource configuration
- Don't: Hardcode resource ARNs or account IDs in templates, use
!Ref,!GetAtt, and!Sub

