aws-serverless

Implements AWS Lambda handlers, API Gateway integrations, and SQS event-driven pipelines with SAM templates.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/nperepichka/Antigravity --skill aws-serverless-nperepichka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-serverless
Source: https://github.com/nperepichka/Antigravity/tree/main/config/skills/aws-serverless
Command: npx skills add https://github.com/nperepichka/Antigravity --skill aws-serverless-nperepichka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @aws-sdk/client-dynamodb, @aws-sdk/lib-dynamodb, boto3.

What problem does it solve? Building serverless applications on AWS involves subtle production pitfalls—SQS batch retry storms, Lambda timeout races, database connection exhaustion, and slow cold starts—that cause outages and cost overruns when handled incorrectly. ## Core Features & Use Cases - Lambda Handler Patterns: Ready-to-use Node.js 20+ and Python 3.12+ handlers with warm-connection reuse, structured error responses, and proper event loop management. - Event-Driven SQS Processing: Partial batch failure handling via ReportBatchItemFailures so only failed messages are retried, plus DLQ configuration. - Infrastructure as Code: A complete AWS SAM template covering HTTP API, DynamoDB single-table design, SQS queues with redrive policies, and ARM64 functions. - Use Case: You need to build a REST API backed by DynamoDB with an asynchronous processing queue. Apply these patterns to get correct visibility timeouts, least-privilege IAM policies, and cold-start-optimized packaging from the start. ## Quick Start Use the aws-serverless skill to scaffold a Lambda function with an HTTP API endpoint, DynamoDB table, and SQS worker following production best practices.

Frequently Asked Questions about aws-serverless

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

FAQPage Schema
How do I handle partial batch failures in SQS Lambda functions?▼

Enable ReportBatchItemFailures on the event source mapping and return an object containing a batchItemFailures array with the messageId of each failed record. SQS then retries only the failed messages instead of the entire batch.

How do I write an AWS Lambda handler in Node.js or Python?▼

Initialize SDK clients outside the handler function so connections are reused across warm invocations, then parse the HTTP method and path parameters from the event. In Node.js, set context.callbackWaitsForEmptyEventLoop = false to prevent open connections from delaying responses.

What SQS visibility timeout should I use with Lambda?▼

Set the queue VisibilityTimeout to at least six times the Lambda function timeout. If the visibility timeout is shorter than the function timeout, in-flight messages become visible again and get processed twice.

Why does my Lambda function exhaust RDS database connections?▼

Hundreds of concurrent Lambda invocations each open their own database connections, overwhelming the RDBMS connection pool. Use Amazon RDS Proxy to pool and share connections across invocations.

How do I reduce Lambda cold start times?▼

Bundle functions with esbuild to remove unused SDK modules, deploy on the ARM64 architecture, and keep the deployment package under 15MB. Initializing clients outside the handler also avoids repeated setup on warm invocations.