Claude Code plugins for AWS development with specialized knowledge and MCP server integrations.
AWS CDK development skill with integrated MCP servers for infrastructure as code.
Features:
- AWS CDK best practices and patterns
- Pre-deployment validation script
- Comprehensive CDK patterns reference
Integrated MCP Servers:
- AWS Documentation MCP (HTTP)
- AWS CDK MCP (stdio)
Cost optimization, monitoring, and operational excellence with 3 integrated MCP servers.
Features:
- Cost estimation and optimization
- Monitoring and observability patterns
- Operational best practices
Integrated MCP Servers:
- AWS Pricing
- AWS Cost Explorer
- Amazon CloudWatch
Serverless and event-driven architecture patterns based on Well-Architected Framework with 2 integrated MCP servers.
Features:
- Well-Architected serverless design principles
- Event-driven architecture patterns
- Orchestration with Step Functions
- Saga patterns for distributed transactions
- Event sourcing patterns
Integrated MCP Servers:
- AWS Documentation MCP (HTTP)
- AWS Serverless MCP (SAM CLI)
Add the marketplace to Claude Code:
/plugin marketplace add zxkane/aws-skillsInstall plugins individually:
/plugin install aws-cdk@aws-skills
/plugin install aws-cost-ops@aws-skills
/plugin install serverless-eda@aws-skillsDo NOT explicitly specify resource names when they are optional in CDK constructs.
// ✅ GOOD - Let CDK generate unique names
new lambda.Function(this, 'MyFunction', {
// No functionName specified
});
// ❌ BAD - Prevents multiple deployments
new lambda.Function(this, 'MyFunction', {
functionName: 'my-lambda',
});Use appropriate constructs for automatic bundling:
- TypeScript/JavaScript:
NodejsFunctionfromaws-cdk-lib/aws-lambda-nodejs - Python:
PythonFunctionfrom@aws-cdk/aws-lambda-python-alpha
Before committing CDK code:
npm run build
npm test
npm run lint
cdk synth
./scripts/validate-stack.shAsk Claude to help with CDK:
Create a CDK stack with a Lambda function that processes S3 events
Claude will:
- Follow CDK best practices
- Use NodejsFunction for automatic bundling
- Avoid explicit resource naming
- Grant proper IAM permissions
- Use MCP servers for latest AWS information
Estimate costs before deployment:
Estimate the monthly cost of running 10 Lambda functions with 1M invocations each
Analyze current spending:
Show me my AWS costs for the last 30 days broken down by service
Set up monitoring:
Create CloudWatch alarms for my Lambda functions to alert on errors and high duration
Investigate issues:
Show me CloudWatch logs for my API Gateway errors in the last hour
Audit activity:
Show me all IAM changes made in the last 7 days
Assess security:
Run a Well-Architected security assessment on my infrastructure
Build serverless applications:
Create a serverless API with Lambda and API Gateway for user management
Implement event-driven workflow:
Create an event-driven order processing system with EventBridge and Step Functions
Orchestrate complex workflows:
Implement a saga pattern for booking flights, hotels, and car rentals with compensation logic
.
├── .claude-plugin/
│ └── marketplace.json # Plugin marketplace configuration
├── skills/
│ ├── aws-cdk-development/ # CDK development skill
│ │ ├── SKILL.md
│ │ ├── references/
│ │ │ └── cdk-patterns.md
│ │ └── scripts/
│ │ └── validate-stack.sh
│ ├── aws-cost-operations/ # Cost & operations skill
│ │ ├── SKILL.md
│ │ └── references/
│ │ ├── operations-patterns.md
│ │ └── cloudwatch-alarms.md
│ └── aws-serverless-eda/ # Serverless & EDA skill
│ ├── SKILL.md
│ └── references/
│ ├── serverless-patterns.md
│ └── eda-patterns.md
└── README.md
MCP server names use short identifiers to comply with Bedrock's 64-character tool name limit. The naming pattern is: mcp__plugin_{plugin}_{server}__{tool}
Examples: awsdocs (AWS docs), cdk (CDK), cw (CloudWatch), sfn (Step Functions), sam (Serverless), etc.
MIT License - see LICENSE