aws-serverless

Builds, deploys, and troubleshoots AWS serverless applications using Lambda, API Gateway, Step Functions, and EventBridge.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill aws-serverless-richardnroman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-serverless
Source: https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform/tree/main/.agents/skills/aws-serverless
Command: npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill aws-serverless-richardnroman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Serverless development on AWS involves dozens of easy-to-miss quotas, mutual-exclusivity rules, and error patterns (502 proxy responses, CORS misconfigurations, concurrency throttling, SnapStart constraints) that cause production incidents. This Skill provides domain expertise and exact reference values for building, deploying, and debugging event-driven architectures on AWS. ## Core Features & Use Cases - Architecture guidance: Pattern selection for REST/HTTP APIs, event processing, orchestration, streaming, fan-out, and scheduled jobs with default-vs-alternative trade-offs. - Exact quotas and gotchas: Lambda memory/CPU mapping, API Gateway throttling limits, SQS/DynamoDB Streams ESM parameters, concurrency control interactions, and Step Functions error semantics. - Troubleshooting playbooks: Error-to-cause-to-fix mappings for 502/504, throttling, SnapStart failures, SAM/CDK deployment errors, plus CloudWatch Logs Insights diagnostic queries. - Use Case: When a Lambda behind API Gateway returns 502 errors, route to the troubleshooting reference to identify the malformed proxy response shape and apply the exact fix. ## Quick Start Ask the agent to help design or debug your AWS serverless application, for example: help me connect a Lambda function to API Gateway with CORS and throttling configured.

Frequently Asked Questions about aws-serverless

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a 502 Bad Gateway error from API Gateway with Lambda?▼

A 502 under Lambda proxy integration means the response shape is malformed. The function must return an object with statusCode, headers, and a body that is a JSON-stringified string, not a raw object. The function itself ran fine; only the response format was wrong.

Should I use SnapStart or Provisioned Concurrency for Lambda cold starts?▼

SnapStart works for Java 11+, Python 3.12+, and .NET 8+ and is mutually exclusive with Provisioned Concurrency. Use Provisioned Concurrency when you need guaranteed sub-50ms latency on every request, EFS, or more than 512 MB ephemeral storage; otherwise try SnapStart first.

What is the difference between API Gateway REST API and HTTP API?▼

HTTP API offers lower latency, native JWT authorizers, and a 30-second hard timeout. REST API adds WAF, API keys, usage plans, request validation, caching, and edge-optimized endpoints, with a 29-second default timeout adjustable for Regional or private APIs.

Why is my SQS-triggered Lambda not scaling fast enough?▼

Standard SQS event source mappings start at 5 concurrent invocations and scale by roughly 300 per minute up to 1,250. For spiky or high-throughput workloads, use Provisioned Mode pollers, noting that Provisioned Mode and Maximum Concurrency are mutually exclusive on the same mapping.

Can Step Functions retry all errors with States.ALL?▼

No. States.ALL does not catch States.DataLimitExceeded or States.Runtime, which are terminal errors. Payloads over 256 KiB must be stored in S3 with keys passed between states rather than retried.

When should I not use this serverless skill?▼

This guidance does not apply to EC2, ECS/Fargate container workloads, or Amplify hosting. It covers Lambda-centric event-driven architectures only; containerized or VM-based deployments need different tooling and references.