Language:JapaneseEnglish

databases-on-aws Claude Code Plugin

Category
Database
Topics
Databases & Storage · Cloud, Deployment & CI/CD · Migration & Modernization
First cataloged
2026-07-09 (UTC)
Explanation last updated
2026-09-15 (UTC)
Source (GitHub) last updated
2026-10-09 (UTC) (6 days ago)

The explanation below is AI-generated. Please verify it against the sources.

databases-on-aws is a Claude Code / Codex / Cursor plugin that packages AWS database expertise as an agent skill, helping developers design schemas, write and run queries, plan migrations, and pick an appropriate database type for a given workload. The plugin bundles an agent skill for Aurora DSQL, an MCP server for AWS documentation and best practices, an MCP server for direct Aurora DSQL operations (disabled by default), and a hook that prompts schema verification after transact operations. It is one of several plugins distributed from the awslabs agent-plugins repository, installable through the Claude Code plugin marketplace or via a manual Codex/Cursor setup. The README notes this plugin's status as only partially available, since only Aurora DSQL support is currently shipped.

About the service

The plugin connects an AI coding assistant to AWS's managed database services. Per the AWS homepage, AWS offers a broad portfolio of purpose-built databases (Aurora, RDS, DynamoDB, ElastiCache, MemoryDB, DocumentDB, Neptune, Keyspaces, Timestream) for different workload types, and per the README the plugin currently operates against Aurora DSQL, AWS's serverless PostgreSQL-compatible distributed SQL database, through a dedicated MCP server that performs live queries, schema changes, and transactions when enabled.

What you can do with databases-on-aws

  • Get guided help designing database schemas for AWS-hosted workloads
  • Get support for writing and running queries and transactions against Aurora DSQL (via an MCP server that is disabled by default)
  • Receive migration guidance for moving workloads onto AWS databases
  • Get recommendations for which AWS database type fits a given workload (relational, key-value, in-memory, document, graph, wide-column, or time-series)
  • Look up AWS documentation and best practices through the awsknowledge MCP server
  • Receive an automatic prompt to verify schema changes and affected rows after transact operations

Sources

Back to list