amazon-opensearch-service

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Amazon OpenSearch Service — the unified skill

Amazon OpenSearch Service — 统一技能指南

This skill answers anything about Amazon OpenSearch Service or Serverless across five capabilities. Step 0 below routes the question to ONE capability and points at that capability's entry-point reference. Everything else — when to dispatch, sub-references, capability-specific facts, cross-capability links — lives in the entry-point reference for that capability.

AWS MCP server is recommended, not required. Capability references show standard AWS CLI commands as the primary syntax (e.g.,
aws opensearch describe-domain
,
aws opensearchserverless create-collection
). Where the AWS MCP server is available, its
call_aws
tool offers a streamlined alternative — but every operation in this skill MUST work via the AWS CLI alone. Data-plane HTTP calls against AOS / AOSS use
awscurl
for SigV4-signed requests; this works in both contexts.

本技能可解答关于Amazon OpenSearch Service或Serverless五大能力的所有问题。下方的步骤0会将问题路由至对应能力模块，并指向该能力的入口参考文档。其他所有内容——如调度时机、子参考文档、能力专属信息、跨能力链接——均存放在对应能力的入口参考文档中。

推荐使用AWS MCP服务器，但非强制要求。 能力参考文档以标准AWS CLI命令作为主要语法示例（如
aws opensearch describe-domain
、
aws opensearchserverless create-collection
）。若可使用AWS MCP服务器，其
call_aws
工具可提供更简化的替代方案——但本技能中的所有操作必须仅通过AWS CLI即可完成。针对AOS/AOSS的数据平面HTTP请求使用
awscurl
进行SigV4签名，该方式在两种环境下均适用。

Step 0: detect the capability — first thing you do

步骤0：识别能力模块——首要操作

Pick one of the five capabilities below. State the detected capability in your first sentence (e.g., "Detected capability: SEARCH — semantic search setup with Bedrock embeddings."). Then load the entry-point reference; that file describes when to dispatch, indexes the rest of the capability's files, and routes you to the next step.

Capability	Entry-point reference
migration — Solr / Elasticsearch / self-managed OpenSearch into AOS or AOSS. Schema/query translation, sizing, cutover.	`references/assessment-workflow.md`
provisioning — Provisioning and managing AOS domains and AOSS collections. Lifecycle, upgrades, storage tiers, FGAC, monitoring.	`references/provisioning-reference.md`
search — Vector / semantic / hybrid / sparse / dense / RAG retrieval. Bedrock connectors, FAISS HNSW vs Lucene.	`references/search-semantic-search-guide.md`
log-analytics — Log search, observability, PPL, OSI ingestion, anomaly detection, OpenSearch Dashboards. Splunk/Datadog/ELK alternatives.	`references/log-analytics-guide.md`
trace-analytics — Distributed traces with OpenTelemetry. Span queries, service maps, Data Prepper.	`references/trace-analytics-trace-queries.md`

If a prompt spans capabilities (e.g., "migrate from Solr AND set up RAG on the new domain"), pick the dominant capability for the response and close with a one-line handoff to the other capability's entry-point ref.

从以下五大能力模块中选择一个。在回复的第一句话中说明识别出的能力模块（例如："识别到能力模块：SEARCH——基于Bedrock嵌入的语义搜索配置。"）。然后加载对应的入口参考文档，该文档会说明调度时机、索引该能力模块的其他文件，并引导您进入下一步操作。

能力模块	入口参考文档
迁移 — 将Solr/Elasticsearch/自托管OpenSearch迁移至AOS或AOSS，包含模式/查询转换、容量规划、切换。	`references/assessment-workflow.md`
配置管理 — 配置并管理AOS域及AOSS集合，包含生命周期、升级、存储层级、FGAC、监控。	`references/provisioning-reference.md`
搜索 — 向量/语义/混合/稀疏/稠密/RAG检索，包含Bedrock连接器、FAISS HNSW与Lucene对比。	`references/search-semantic-search-guide.md`
日志分析 — 日志搜索、可观测性、PPL、OSI数据摄入、异常检测、OpenSearch Dashboards，包含Splunk/Datadog/ELK替代方案。	`references/log-analytics-guide.md`
追踪分析 — 基于OpenTelemetry的分布式追踪，包含跨度查询、服务地图、Data Prepper。	`references/trace-analytics-trace-queries.md`

若请求涉及多个能力模块（例如："从Solr迁移并在新域上配置RAG"），请选择主要能力模块进行回复，并在结尾用一句话引导至其他能力模块的入口参考文档。

Universal rules (apply to ALL capabilities)

通用规则（适用于所有能力模块）

These rules apply to every response, regardless of capability. Capability-specific rules (sizing math, shape detection, Migration Assistant for Amazon OpenSearch Service capability matrix, k-NN engine selection) live in the entry-point references, not here.

Report header (every multi-section response). Begin every multi-section response with a single fenced metadata block:
```
> Generated: <ISO 8601 timestamp> | Skill: amazon-opensearch-service v<N>
```
. Get the time by calling the
```
current_time
```
tool (returns ISO 8601 in UTC). Read the skill version from this file's frontmatter
```
version:
```
field. For one-line answers (terse FOCUSED_OPERATIONAL replies, anti-pattern refusals) the header is optional; for any multi-section deliverable it is REQUIRED. Place it immediately after the report title and before the first
```
##
```
heading.
No dollar estimates (HARD CONSTRAINT). Never produce
```
$X/month
```
,
```
~$1,500
```
, or any dollar figure. Route every cost question to https://calculator.aws and stop. If a sub-reference contains dollar figures, treat them as informational context only and do NOT pass them through to the user.
No credential leakage (HARD CONSTRAINT). Never include master usernames, KMS key ARNs, VPC endpoint URLs, instance IPs, or account IDs in generated output.
Pick one for every A-vs-B decision. Name a primary recommendation in one line with a one-sentence reason. A "go with B if..." caveat is allowed AFTER the primary; never lead with conditional-only guidance.
Source restatement. The first 2–3 sentences must restate the source (engine + version + scale) when known, or restate the customer's question in concrete terms. The very first text the user sees must NOT be tool narration, meta-commentary, the report title, or simply restating the question verbatim.
No marketing tone. Do NOT use "seamless", "robust", "best-in-class", "production-hardened", "enterprise-grade", "world-class", "cleanly", "elegant". Do NOT stack 3+ vague hedges ("typically", "generally", "usually", "in most cases") in a single recommendation — be specific about when it does and does not apply.
Cross-capability handoff. When a user prompt spans capabilities (e.g., "migrate from Solr AND set up RAG on the new domain"), pick the dominant capability for the response, then close with a one-line handoff: "For <other capability>, see
references/<other-capability>-<entry>.md
."

这些规则适用于所有回复，无论涉及哪个能力模块。能力模块专属规则（容量计算、形态检测、Migration Assistant for Amazon OpenSearch Service能力矩阵、k-NN引擎选择）均存放在入口参考文档中，而非此处。

报告头（多章节回复必填）。 所有多章节回复需以一个围栏式元数据块开头：
```
> Generated: <ISO 8601 timestamp> | Skill: amazon-opensearch-service v<N>
```
。通过调用
```
current_time
```
工具获取时间（返回UTC时区的ISO 8601格式时间）。从本文件的前置字段
```
version:
```
中读取技能版本。对于单行回复（简洁的FOCUSED_OPERATIONAL回复、反模式拒绝），报告头为可选；但对于任何多章节交付内容，报告头为必填项。需将其放在报告标题之后、第一个
```
##
```
标题之前。
禁止估算费用（硬性约束）。不得生成
```
$X/month
```
、
```
~$1,500
```
或任何金额数字。所有费用相关问题均需引导至https://calculator.aws，并停止回复。若子参考文档中包含金额数字，仅将其视为信息背景，不得传递给用户。
禁止泄露凭证（硬性约束）。生成的输出内容中不得包含主用户名、KMS密钥ARN、VPC终端节点URL、实例IP或账户ID。
二选一决策。针对所有A/B决策，需用一句话给出主要推荐方案及理由。可在主要推荐之后补充*"若...则选择B"*的说明，但不得仅以条件性引导作为开头。
来源重述。若已知信息，开头2-3句话必须重述来源（引擎+版本+规模）；否则需将客户的问题转化为具体表述。用户看到的第一部分内容不得是工具说明、元评论、报告标题或直接复述问题原文。
禁用营销语气。不得使用*"无缝"、"强大"、"顶尖"、"生产级"、"企业级"、"世界级"、"简洁"、"优雅"等词汇。不得在单个推荐中堆叠3个及以上模糊修饰词（如"通常"、"一般"、"往往"、"大多数情况下"*）——需明确说明适用及不适用场景。
跨能力模块引导。若用户请求涉及多个能力模块（例如："从Solr迁移并在新域上配置RAG"），选择主要能力模块进行回复，然后在结尾用一句话引导："关于<其他能力模块>，请参阅
references/<other-capability>-<entry>.md
。"

Cross-cutting references (used across multiple capabilities)

跨领域参考文档（适用于多个能力模块）

These references are not capability-prefixed because they apply across capabilities. Capability entry-point references load them when relevant; SKILL.md never loads them directly.

```
references/sizing.md
```
— sizing math, instance family details, OR1 trade-offs, watermarks, JVM heap rules.
```
references/vector-knn.md
```
— k-NN engines, memory math, RAG ingestion patterns, ELSER alternatives.
```
references/observability.md
```
— log analytics patterns, ISM, UltraWarm/Cold tiering, Splunk/Datadog migration playbooks.
```
references/security.md
```
— FGAC, encryption, VPC patterns, audit logs, compliance posture.
```
references/personas.md
```
— communication style per persona.
```
references/assessment-gotchas.md
```
— production gotcha catalog (cite by number in Migration specifics or Risks/blockers tables; each gotcha carries a
```
Category:
```
tag that determines its lane).
```
references/assessment-knowledge-retrieval.md
```
— topic → tool → URL recipe for batched verification.

Assets (

assets/

): report templates for FULL_ASSESSMENT renderings (Solr-source, ES-source, executive summary).

这些参考文档未添加能力模块前缀，因为它们适用于多个能力模块。能力模块的入口参考文档会在相关时加载这些文档；SKILL.md不会直接加载它们。

```
references/sizing.md
```
— 容量计算、实例系列详情、OR1权衡、水位线、JVM堆规则。
```
references/vector-knn.md
```
— k-NN引擎、内存计算、RAG数据摄入模式、ELSER替代方案。
```
references/observability.md
```
— 日志分析模式、ISM、UltraWarm/冷存储层级、Splunk/Datadog迁移手册。
```
references/security.md
```
— FGAC、加密、VPC模式、审计日志、合规态势。
```
references/personas.md
```
— 针对不同角色的沟通风格。
```
references/assessment-gotchas.md
```
— 生产环境问题目录（在迁移详情或风险/障碍表格中按编号引用；每个问题带有
```
Category:
```
标签，用于确定其所属领域）。
```
references/assessment-knowledge-retrieval.md
```
— 批量验证的主题→工具→URL指南。

资源目录(

assets/

)：FULL_ASSESSMENT报告模板（Solr源、ES源、执行摘要）。

What this skill does NOT do

本技能不支持的操作

Estimate dollar costs. Pricing changes monthly and account-specific (RI, Savings Plan, EDP) discount math is outside this skill's reliable scope. Use https://calculator.aws.
Move data. Use Migration Assistant for Amazon OpenSearch Service (Historical Data Migration for backfill, Live Traffic Migration for live cutover).
Build embedding models. Use Amazon Bedrock or SageMaker.
Replace Splunk SPL or Datadog APM 1:1. Some queries / detectors / dashboards need rewriting.
Tune relevance for a specific catalog. Use OpenSearch Benchmark
```
big5
```
workload + your own judgment list.

估算费用。价格每月变动，且账户专属折扣（RI、Savings Plan、EDP）的计算超出本技能的可靠范围。请使用https://calculator.aws。
迁移数据。请使用Migration Assistant for Amazon OpenSearch Service（Historical Data Migration用于回填数据，Live Traffic Migration用于实时流量切换）。
构建嵌入模型。请使用Amazon Bedrock或SageMaker。
一对一替代Splunk SPL或Datadog APM。部分查询/检测器/仪表板需要重写。
针对特定目录调优相关性。请使用OpenSearch Benchmark
```
big5
```
工作负载+您自己的判断列表。