Aws Aurora
CheckedProvides AWS guidance and assistance for deploying and managing cloud infrastructure.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add alinaqi/maggy --skill aws-aurora -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
alinaqi
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned alinaqi/claude-bootstrap at 72a456e6cc.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 72a456e6cc
- Manifest
- skills/aws-aurora/SKILL.md
- Scanned
- 1 file, 593 lines
About this skill
What it does
This skill provides guidance and assistance for deploying and managing Amazon Aurora, a MySQL/PostgreSQL-compatible relational database service. It focuses on best practices for serverless architectures, emphasizing connection management strategies using RDS Proxy or Data API to avoid direct connections from Lambda functions. The skill covers different Aurora deployment options like Serverless v2, Provisioned, and Global, along with connection strategies optimized for various workloads.
When to use it
- When deploying an Aurora database for a serverless application (e.g., using AWS Lambda).
- For setting up high availability and disaster recovery solutions utilizing Aurora Global.
- To optimize connection management and concurrency when dealing with variable or predictable workloads.
- When needing simple HTTP access to Aurora Serverless without requiring a VPC, leveraging the Data API.
Key capabilities
- Provides guidance on using RDS Proxy for connection pooling and automatic failover handling.
- Explains how to use the Data API for simplified serverless access to Aurora.
- Covers different Aurora deployment options: Serverless v2, Provisioned, and Global.
- Offers examples of CDK code snippets for setting up an RDS Proxy.
- Details connection strategies optimized for Lambda functions, application servers (ECS/EC2), and serverless environments.
Example prompts
- "How do I connect my AWS Lambda function to Aurora using RDS Proxy?"
- "What are the benefits of using Aurora Data API?"
- "Explain the differences between Aurora Serverless v2 and Aurora Provisioned."
- “Show me an example CDK code for creating an RDS proxy.”
Tips & gotchas
- For Lambda functions, always use RDS Proxy or Data API to manage connections. Avoid direct raw connections.
- Aurora Global is specifically designed for multi-region deployments and disaster recovery scenarios.
- Data API introduces higher latency per query compared to using RDS Proxy.