RFC: AWS Serverless plugin

[bfreiberg]

Is this related to an existing feature request or issue?

No response

Summary

Add a plugin to help developers design, build, deploy and debug applications using AWS Serverless services, especially AWS Lambda

Use case

Web applications, event-driven applications, orchestration and workflows, data processing. Governance, optimization and observability of serverless applications

Proposal

The plugin will contain skills for certain general aspects (such as optimization, troubleshooting, etc.) and skills for specific features (like durable functions, managed instances, etc.). The skills are

aws-lambda
Purpose: Build serverless applications with AWS Lambda, event sources, API Gateway, EventBridge, and Step Functions
Trigger intent: "Lambda function", "event source", "API Gateway", "EventBridge", "Step Functions", "serverless API", "event-driven architecture", "DynamoDB stream", "SQS queue"

aws-serverless-deployment
Purpose: Deploy serverless applications using SAM and CDK with project scaffolding, IaC templates, and CI/CD pipelines
Trigger intent: "SAM template", "SAM init", "SAM deploy", "CDK serverless", "CDK Lambda construct", "NodejsFunction", "PythonFunction", "serverless CI/CD pipeline"

aws-lambda-durable-functions
Purpose: Build resilient, long-running Lambda workflows with automatic state persistence, retry logic, and orchestration for up to 1 year execution
Trigger intent: "durable functions", "Lambda workflow", "checkpoint", "long-running Lambda", "saga pattern", "stateful Lambda", "human-in-the-loop", "agentic workflow"

The plugin depends on the AWS Serverless MCP.

Out of scope

Changes to the AWS Serverless MCP server which could be helpful to these skills

Potential challenges

Offering a cohesive experience for the user while aggregating multiple skills

Dependencies and Integrations

No response

Alternative solutions

[bfreiberg]

Created #49 with initial implementation

[krokoko]

Thanks @bfreiberg ! Initial feedback:

Summary

The proposal adds an aws-serverless plugin with three skills (aws-lambda, aws-serverless-deployment, aws-lambda-durable-functions), an MCP server, a SAM validation hook, and marketplace updates. The plugin is focused on serverless/Lambda and fits the “one cohesive purpose” idea, but the RFC and implementation need more detail and several design choices should be aligned with the Design Guidelines and Maintainers Guide.

What works well

Focused domain — “AWS Serverless / Lambda” is a clear, cohesive scope (design guideline: “Keep plugins focused”).
Skill split — Three skills (lambda runtime/events, deployment, durable functions) respect “single responsibility per skill.”
MCP + hooks — Using the AWS Serverless MCP and a SAM template validation hook fits the plugin model.
Related RFC — #48 is linked and gives high-level motivation.

Requests

Could you please:

• update RFC with: (1) the three skill names and one-sentence purpose + trigger intent for each, (2) that the plugin depends on the AWS Serverless MCP, (3) how it differs from or complements the existing deploy-on-aws plugin
• Consider trimming or merging references (e.g. “advanced-patterns” or “troubleshooting” might be combinable or split differently) to stay within the 50–100 line guidance if files exceeds that.
• deploy-on-aws already covers: CDK project setup and patterns, IaC generation, deployment workflow. Aws-serverless-deployment would add: SAM and CDK project setup, CDK constructs/patterns, CI/CD, SAM/CDK coexistence. Risk: Two plugins both teaching “CDK project setup” and “CDK patterns” can confuse the agent (which plugin to trigger) and duplicate content. In the RFC: clearly state that deploy-on-aws = “get my app onto AWS (pick services, cost, full IaC/deploy)” and aws-serverless = “I’m already going serverless; help me with Lambda, event sources, Step Functions, SAM/CDK serverless patterns, durable functions.”. In skill descriptions/frontmatter: include trigger phrases that steer “deploy this app to AWS” → deploy-on-aws and “Lambda event sources / Step Functions / SAM / durable functions” → aws-serverless.

[rohanmeh]

@krokoko are you intending to add terraform in deploy-on-aws?

[krokoko]

Closing as merged