add-aurora-mysql

Automate schema-per-tenant Aurora MySQL repository setup with KMS encryption and reusable pools.

Updated Mar 23, 2026

Search Tags:#typescript #lambda #tenancy #multitenancy #pooling #database-migration #aurora-mysql

Ready to run

npx skills add https://github.com/tcelestino/softplan-engineering-skills --skill add-aurora-mysql

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-aurora-mysql
Source: https://github.com/tcelestino/softplan-engineering-skills/tree/main/skills/add-aurora-mysql
Command: npx skills add https://github.com/tcelestino/softplan-engineering-skills --skill add-aurora-mysql

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines adding a per-tenant Aurora MySQL repository with a reusable connection pool and KMS-based encryption to ensure isolation and performance in serverless Lambda apps.

Core Features & Use Cases

Schema-per-tenant isolation using dedicated schemas per tenant.
Reusable connection pool across Lambda invocations to reduce cold start latency.
KMS encryption support checked at the RDS cluster level; credentials management via Secrets Manager in production.
Guidance to implement repository pattern, migrations, and tenant-aware data access.

Quick Start

Provide the entity name when prompted to scaffold a tenant-scoped Aurora MySQL repository in your microservice.

Frequently Asked Questions about add-aurora-mysql

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

FAQPage Schema

How do I set up schema-per-tenant Aurora MySQL isolation in a Lambda microservice?▼

Schema-per-tenant isolation is automated by provisioning dedicated schemas per tenant, combined with a reusable connection pool and KMS encryption to ensure secure, performant data access in serverless Lambda apps.

What is the best way to reduce Aurora MySQL cold start latency for multi-tenant Lambda functions?▼

To reduce cold start latency in multi-tenant Lambda functions, use a reusable connection pool shared across Lambda invocations. This maintains database connections efficiently, minimizing startup overhead for Aurora MySQL access.

Can I use AWS Secrets Manager for Aurora MySQL credentials in a multi-tenant migration?▼

Yes, AWS Secrets Manager can be used for credentials management in production environments. The setup integrates Secrets Manager for secure credential handling while scaffolding per-tenant migrations for your Aurora MySQL database.

Does Aurora MySQL schema-per-tenant architecture support KMS encryption at the cluster level?▼

Yes, KMS encryption is supported and checked at the RDS cluster level. This ensures your tenant-isolated Aurora MySQL schemas maintain secure data encryption standards across the entire database cluster.

How do I implement per-tenant database migrations for an Aurora MySQL repository?▼

Per-tenant database migrations are implemented by scaffolding a tenant-aware repository pattern. This guides tenant schema selection and pool provisioning, allowing you to apply migrations independently to each tenant's schema.