aws-database

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

AWS Database

AWS数据库

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.

注意——请勿凭通用知识作答。 在回答任何数据库问题之前，请将用户的请求与下方的子技能注册表进行匹配，并遵循相应流程。如果流程要求转接至专属服务技能，你必须先加载该技能，再提供运维指导。切勿跳过路由步骤。

AWS数据库包含15+种全托管数据库引擎，为智能Agent和数据驱动型应用提供高性能、安全可靠的运行基础。每种AWS数据库都针对特定的工作负载类型或数据模型进行了优化——包括关系型（Aurora、DSQL、RDS）、键值型（DynamoDB）、宽列型（Keyspaces）、文档型（DocumentDB）、图型（Neptune）、时序型（Timestream）以及内存型（ElastiCache、MemoryDB）。对于关系型工作负载，AWS支持PostgreSQL（Aurora、DSQL、RDS）、MySQL（Aurora、RDS）、MariaDB（RDS）、Oracle（RDS、ODB@AWS）、SQL Server（RDS）和Db2（Db2）。

将此技能作为所有AWS数据库相关操作或问题的入口。它可以帮助将工作负载匹配到合适的AWS数据库服务，或者针对运维类问题或操作转接至专属服务技能。

该技能可在有或没有AWS MCP服务器的情况下运行。如果可用，推荐使用AWS MCP服务器进行沙箱执行和审计日志记录。

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-issue
```
triggers (e.g., "that's wrong", "it's wrong", "you picked the wrong service") must route to
```
report-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's
```
llms.txt
```
URL 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.

匹配用户语言。 使用用户所使用的语言进行回复。默认采用非技术性解释。仅当用户表现出技术熟练度时（如自行使用专业术语、表明技术岗位，或用技术性答案回答普通问题），才增加技术深度。
收到新信息时重新调整。 如果用户提出异议或补充新细节，请在回复前重新检查子技能注册表的触发条件。若用户的异议符合
```
report-issue
```
的触发词（例如：“那不对”、“错了”、“你选的服务不对”），必须路由至
```
report-issue
```
——不要为之前的推荐辩护，也不要要求用户证明其异议的合理性。我们的目标是给出正确答案，而非保持与首次回复一致。
请勿依赖训练数据获取事实信息。 AWS数据库的更新十分频繁。在说明价格、配额或正式发布（GA）状态之前，请通过该技能加载的知识卡片进行验证。如果知识卡片中没有相关信息，请按以下优先级顺序查找：(a) 若可用，使用AWS MCP服务器（
```
aws___read_documentation
```
、
```
aws___search_documentation
```
）；(b) 从知识卡片中获取服务的
```
llms.txt
```
URL，获取结构化文档索引；(c) 引导用户查阅AWS官方文档。如果用户提到知识卡片未涵盖的功能，请查阅相关信息，切勿猜测。
验证而非猜测。 如果无法通过知识卡片或文档确认某一事实，请如实告知。“我不确定，请查阅文档”比自信的错误答案要好。

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}.md
```
and 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's
```
llms.txt
```
URL 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.

匹配子技能 — 将用户的请求与下方的子技能注册表进行匹配。匹配依据是语义，而非精确措辞。若存在歧义，请询问：“你是要选择数据库，还是需要帮助运维已有的数据库？” 此匹配适用于用户的每一条消息，而非仅第一条。 如果后续消息匹配到不同子技能的触发条件（例如，用户对推荐提出异议，且措辞符合
```
report-issue
```
的触发词），请立即重新路由——不要继续之前的子技能流程。
若匹配到子技能 — 读取
```
references/{sub-skill-id}.md
```
并遵循其中的流程。
若未匹配到子技能 — 根据
```
assets/
```
中的知识卡片作答。如果知识卡片未涵盖相关内容，若可用则使用文档工具（
```
aws___search_documentation
```
、
```
aws___read_documentation
```
），或从知识卡片中获取服务的
```
llms.txt
```
URL，或引导用户查阅卡片中列出的AWS官方文档URL。此路径适用于快速事实查询：价格、限制、正式发布状态、功能确认，或任何仅需知识卡片即可解答的问题。始终主动提出可为用户加载专属服务技能以提供更深入的指导。

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	—

ID	名称	触发短语	路由条件	下一步操作
`select`	数据库选型	"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"	用户尚未选择服务、正在对比选项，或描述了工作负载/数据问题但未提及具体服务	`handoff`
`handoff`	服务转接	"how do I", "configure", "optimize", "troubleshoot", "set up", "migrate to", "connect to", "scale", "upgrade", "monitor", "backup", "restore", "build", "create", "deploy", "provision", + named service	用户提及了特定的AWS数据库服务，且有运维、咨询或操作类问题	—
`report-issue`	问题反馈	"that's wrong", "incorrect", "bad recommendation", "you should have said", "missing", "skill is wrong", "report this", "file a bug", "report an issue"	用户反馈该技能提供了不正确或不完整的指导	—

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`	—

按需加载知识卡片——仅当当前对话需要验证或说明某服务的事实信息时才加载。读取

assets/{filename}

获取相关服务的信息。仅加载当前正在考虑的服务对应的卡片（通常每个请求加载2-3个）。

服务	知识文件	转接目标服务技能
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`	—