aws-database

Routes AWS database selection and operational questions to service-specific skills and knowledge cards.

2.5k|282|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill aws-database
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-database
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/plugins/aws-core/skills/aws-database
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill aws-database

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Choosing among 15+ AWS database services is error-prone, and AI training data often contains outdated facts about pricing, features, and limitations. This Skill routes any AWS database question to the correct decision procedure or service-specific skill, grounding answers in maintained knowledge cards instead of stale general knowledge.

Core Features & Use Cases

  • Database Selection Guidance: Matches workloads to the right service across relational (Aurora, DSQL, RDS), key-value (DynamoDB), wide-column (Keyspaces), document (DocumentDB), graph (Neptune), time-series (Timestream), and in-memory (ElastiCache, MemoryDB) models, with distinct paths for new applications, migrations, and refactors.
  • Service Skill Handoff: Loads deeper service-specific skills via local install, AWS MCP server, or the Agent Toolkit CLI before giving operational guidance on provisioning, configuration, or troubleshooting.
  • Verified Facts via Knowledge Cards: Answers quick questions on pricing, free tiers, limitations, and GA status from per-service knowledge cards, falling back to AWS documentation tools.
  • Use Case: A developer says "I'm building a serverless app that needs a SQL database." The Skill disambiguates serverless operations vs. capacity, compares Aurora DSQL against Aurora PostgreSQL, recommends one with a credible alternative, and offers to load the service skill for setup.

Quick Start

Ask the agent which AWS database to use for your application, describing your data model, scale expectations, and whether it is a new build, migration, or refactor.

Frequently Asked Questions about aws-database

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

FAQPage Schema
How do I choose the right AWS database for my application?

Describe your workload, data model, and scale, and the Skill routes you through a selection procedure covering new applications, migrations, and refactors. It recommends one service with reasoning, one credible alternative, and what would change the answer.

Aurora DSQL vs Aurora PostgreSQL: which should I use?

Aurora DSQL is the default for new applications needing serverless operations, instant scale-to-zero, and multi-region active-active writes. Choose Aurora PostgreSQL when you need extensions like pgvector or PostGIS, stored procedures, or triggers that DSQL does not support.

Does this skill help migrate an existing database to AWS?

Yes, the migration path maps your source engine to its AWS managed equivalent, such as MongoDB to DocumentDB or Cassandra to Keyspaces. For engine changes, the refactor path recommends targets like Aurora PostgreSQL and names AWS SCT and DMS as tooling.

Can I get operational help for a specific AWS database service?

Yes, when you name a specific service the Skill hands off to a dedicated service skill loaded via local install, the AWS MCP server, or npx skills add. If no service skill exists, it answers from the knowledge card and AWS documentation.

When should I use MemoryDB instead of ElastiCache?

Default to ElastiCache for caching, durable primary storage, and multi-region reads at lower cost with a serverless option. Choose MemoryDB only when you explicitly need active-active writes across multiple Regions, which ElastiCache's read-only cross-region replicas cannot provide.

What are the limitations of the database recommendations?

The Skill picks one primary database and does not design multi-service architectures, generate infrastructure code, or provide schema and query help. Those tasks are handed off to service-specific skills or AWS documentation after selection.