AWS Database
OfficialFreeStreamline your AWS database tasks with precision.
Free · Opens the source repo
What AWS Database does
The AWS Database skill is designed to assist users in navigating the complex landscape of AWS database services. It routes user inquiries related to database selection, operation, and management to the appropriate service-specific skills. This skill is particularly valuable for developers and designers who are building applications on AWS that require data storage and retrieval, ensuring that they can make informed decisions about which database service to use based on their specific workload needs.
With support for a wide range of database types including relational (such as Aurora and RDS), key-value (DynamoDB), document (DocumentDB), and graph databases (Neptune), this skill provides users with the necessary guidance to choose the right database for their application. It supersedes general knowledge with up-to-date service information, ensuring that users have access to the latest features, limitations, and operational procedures. This is crucial in a rapidly evolving cloud environment where database capabilities can change frequently.
The skill operates by matching user requests against a sub-skill registry, ensuring that users receive tailored responses based on their specific needs. Whether a user is looking to start a new project or troubleshoot an existing database setup, the AWS Database skill directs them to the correct resources and knowledge cards. This structured approach minimizes the risk of misinformation and enhances the overall user experience when working with AWS databases.
When to use it
Use this skill when you are planning to build an application on AWS that requires a database, or when you need help with an existing AWS database service.
When not to use it
This skill may not be suitable for users who are not working within the AWS ecosystem or who require database solutions outside of AWS services.
What you can build with it
Choosing a Database for a New Project
When starting a new application on AWS, this skill helps you identify the most suitable database service based on your data model and workload.
Troubleshooting an Existing Database
If you're facing issues with your AWS database, this skill can direct you to the right service-specific guidance for troubleshooting.
Comparing AWS Database Options
When you need to compare different AWS database services, this skill provides insights and recommendations tailored to your specific needs.
How to install AWS Database
View source1. Install with the skills CLI
npx skills add aws/agent-toolkit-for-aws/aws-database --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by awsAWS Database
STOP — Do not answer from general knowledge. Before responding to any database question, match the user's request against the sub-skill registry below and follow its procedure. If the procedure says to hand off to a service skill, you MUST load that skill before providing operational guidance. Never skip the routing step.
AWS Databases comprise 15+ fully-managed database engines and offer a high-performance, secure, and reliable foundation to power agentic AI and data-driven applications. Each AWS database is optimized for a specific workload shape or data model — relational (Aurora, DSQL, RDS), key-value (DynamoDB), wide-column (Keyspaces), document (DocumentDB), graph (Neptune), time-series (Timestream), and in-memory (ElastiCache, MemoryDB). For relational workloads, AWS supports PostgreSQL (Aurora, DSQL, RDS), MySQL (Aurora, RDS), MariaDB (RDS), Oracle (RDS, ODB@AWS), SQL Server (RDS), and Db2 (Db2).
Use this skill as the entry point for any actions or questions related to databases on AWS. It helps match a workload to the right AWS database service, or hand off to a service-specific skill for operational questions or actions.
This skill works with or without the AWS MCP server. When available, the AWS MCP server is recommended for sandboxed execution and audit logging.
Global rules
-
Match the user's language. Respond in the same language the user writes in. Default to non-technical explanations. Only escalate technical depth when they've shown fluency — by using the terms themselves, stating a technical role, or answering a plain question with a technical answer.
-
Revise when new information arrives. If the user pushes back or adds new details, re-check the sub-skill registry triggers before responding. Pushback that matches
report-issuetriggers (e.g., "that's wrong", "it's wrong", "you picked the wrong service") must route toreport-issue— do not defend your prior recommendation or ask the user to justify their objection. The goal is the right answer, not consistency with your first response. -
Do not rely on training data for facts. AWS databases change frequently. Before stating pricing, quotas, or GA status, verify against the knowledge cards loaded by this skill. If the fact is not in a knowledge card, look it up — in priority order: (a) use the AWS MCP server (
aws___read_documentation,aws___search_documentation) if available; (b) fetch the service'sllms.txtURL from its knowledge card for a structured documentation index; (c) direct users to AWS documentation. If a user mentions a feature not covered by a knowledge card, look it up rather than guessing. -
Verify, don't guess. If you cannot confirm a fact from a knowledge card or documentation, say so. "I'm not sure — check the docs" is better than a confident wrong answer.
How this skill works
-
Find the sub-skill — Match the user's request against the sub-skill registry below. Match on meaning, not exact wording. If ambiguous, ask: "Are you choosing a database, or do you need help with one you already have?" This matching applies to every user message, not just the first. If a subsequent message matches a different sub-skill's triggers (e.g., the user pushes back on a recommendation and their phrasing matches
report-issue), re-route immediately — do not continue the previous sub-skill's flow. -
If a sub-skill matches — read
references/{sub-skill-id}.mdand follow its procedure. -
If no sub-skill matches — answer from the knowledge cards in
assets/. If the card doesn't cover it, use documentation tools (aws___search_documentation,aws___read_documentation) if available, or fetch the service'sllms.txtURL from its knowledge card, or direct the user to the AWS documentation URL listed in the card. This is the path for quick facts: pricing, limits, GA status, feature confirmation, or any question answerable from the card alone. Always offer to load the service skill for deeper guidance.
Sub-skill registry
| ID | Name | Trigger Phrases | When to Route Here | Next Steps |
|---|---|---|---|---|
select | Database Selection | "which database", "help me choose", "recommend", "what should I use", "starting a new project", "picking a database", "I need a database", "I'm building", "build a", "how should I store", "best way to handle", "need to support", "design for" | User hasn't chosen a service yet, is comparing options, or describes a workload/data problem without naming a specific service | handoff |
handoff | Service Handoff | "how do I", "configure", "optimize", "troubleshoot", "set up", "migrate to", "connect to", "scale", "upgrade", "monitor", "backup", "restore", "build", "create", "deploy", "provision", + named service | User names a specific AWS database service and has an operational, advisory, or action question | — |
report-issue | Report Issue | "that's wrong", "incorrect", "bad recommendation", "you should have said", "missing", "skill is wrong", "report this", "file a bug", "report an issue" | User reports that the skill gave incorrect or incomplete guidance | — |
Service reference
Load knowledge cards on demand — only when the current turn requires verifying or stating facts about a service. Read assets/{filename} for the relevant service(s). Load only the cards for services being actively considered (typically 2–3 per request).
| Service | Knowledge file | Service skill for handoff |
|---|---|---|
| Aurora DSQL | assets/aurora-dsql.md | aurora-dsql |
| Aurora MySQL | assets/aurora-mysql.md | amazon-aurora-mysql |
| Aurora PostgreSQL | assets/aurora-postgresql.md | amazon-aurora-postgresql |
| DocumentDB | assets/documentdb.md | amazon-documentdb |
| DynamoDB | assets/dynamodb.md | — |
| ElastiCache | assets/elasticache.md | amazon-elasticache |
| Keyspaces | assets/keyspaces.md | amazon-keyspaces |
| MemoryDB | assets/memorydb.md | — |
| Neptune | assets/neptune.md | — |
| ODB @ AWS | assets/odb-aws.md | — |
| RDS for Db2 | assets/rds-db2.md | rds-db2 |
| RDS for MariaDB | assets/rds-mariadb.md | rds-oss |
| RDS for MySQL | assets/rds-mysql.md | rds-oss |
| RDS for Oracle | assets/rds-oracle.md | rds-oracle |
| RDS for PostgreSQL | assets/rds-postgresql.md | rds-oss |
| RDS for SQL Server | assets/rds-sqlserver.md | rds-sqlserver |
| Timestream | assets/timestream.md | — |
Frequently asked questions about AWS Database
Similar skills
ClickHouse Logs Queries
Efficiently manage Supabase logs with ClickHouse SQL.
EF Core D2 Database Diagram Generator
Visualize your EF Core models as D2 diagrams effortlessly.
Safe SQL Execution
Ensure secure SQL execution in Supabase applications.
Oracle to PostgreSQL Migration
Identify migration risks between Oracle and PostgreSQL.
SSMA Console
Streamline Oracle to SQL Server migrations with ease.
SQL Performance Optimization
Enhance SQL query efficiency across all databases.