Aws Aurora

Handles AWS Aurora setup with a laser focus on the connection problem that kills most serverless database projects. The skill pushes you toward RDS Proxy for Lambda functions (connection pooling, IAM auth) or Data API if you want HTTP access without VPC complexity. Includes working TypeScript and Python examples for both approaches, plus CDK snippets for proxy configuration. The core principle is sound: never open raw Aurora connections from Lambda. If you're wrestling with "too many connections" errors or trying to figure out connection pooling for serverless, this covers the two viable patterns with actual code you can adapt.

skills.sh installs: 186
GitHub stars: 685
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add alinaqi/claude-bootstrap --skill aws-aurora --agent claude-code

Installs into .claude/skills of the current project.

Files

AWS Aurora Skill

Amazon Aurora is a MySQL/PostgreSQL-compatible relational database with serverless scaling, high availability, and enterprise features.

Sources: Aurora Docs | Serverless v2 | RDS Proxy

Core Principle

Use RDS Proxy for serverless, Data API for simplicity, connection pooling always.

Aurora excels at ACID-compliant workloads. For serverless architectures (Lambda), always use RDS Proxy or Data API to handle connection management. Never open raw connections from Lambda functions.

Aurora Options

Option	Best For
Aurora Serverless v2	Variable workloads, auto-scaling (0.5-128 ACUs)
Aurora Provisioned	Predictable workloads, maximum performance
Aurora Global	Multi-region, disaster recovery
Data API	Serverless without VPC, simple HTTP access
RDS Proxy	Connection pooling for Lambda, high concurrency