amazon-opensearch-service

Name: amazon-opensearch-service
Author: aws

1.1kinstalls190forks

How to install amazon-opensearch-service?

aws/agent-toolkit-for-aws/amazon-opensearch-service

$npx -y skills add aws/agent-toolkit-for-aws --skill amazon-opensearch-service

Installs into the current project.

Summary

Amazon OpenSearch Service and Serverless across five capabilities — migration (Solr/ES/self-managed OpenSearch into AOS/AOSS, schema/query translation, sizing, cutover); provisioning (domain + AOSS lifecycle, upgrades, storage tiers, FGAC, monitoring); search (vector / semantic /

Files · 1

View on GitHub

SKILL.md

1	# Amazon OpenSearch Service — the unified skill
2
3	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.
4
5	> 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.
6
7	## Step 0: detect the capability — first thing you do
8
9	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.
10
11	\| Capability \| Entry-point reference \|
12	\|---\|---\|
13	\| migration — Solr / Elasticsearch / self-managed OpenSearch into AOS or AOSS. Schema/query translation, sizing, cutover. \| [`references/assessment-workflow.md`](references/assessment-workflow.md) \|
14	\| provisioning — Provisioning and managing AOS domains and AOSS collections. Lifecycle, upgrades, storage tiers, FGAC, monitoring. \| [`references/provisioning-reference.md`](references/provisioning-reference.md) \|
15	\| search — Vector / semantic / hybrid / sparse / dense / RAG retrieval. Bedrock connectors, FAISS HNSW vs Lucene. \| [`references/search-semantic-search-guide.md`](references/search-semantic-search-guide.md) \|
16	\| log-analytics — Log search, observability, PPL, OSI ingestion, anomaly detection, OpenSearch Dashboards. Splunk/Datadog/ELK alternatives. \| [`references/log-analytics-guide.md`](references/log-analytics-guide.md) \|
17	\| trace-analytics — Distributed traces with OpenTelemetry. Span queries, service maps, Data Prepper. \| [`references/trace-analytics-trace-queries.md`](references/trace-analytics-trace-queries.md) \|
18
19	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.
20
21	## Universal rules (apply to ALL capabilities)
22
23	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.
24
25	- 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.
26	- 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.
27	- No credential leakage (HARD CONSTRAINT). Never include master usernames, KMS key ARNs, VPC endpoint URLs, instance IPs,

People who liked this also viewed

6 picks

Type

amazon-opensearch-service

1.1kinstalls190forks

View on GitHub

How to install amazon-opensearch-service?

aws/agent-toolkit-for-aws/amazon-opensearch-service

$npx -y skills add aws/agent-toolkit-for-aws --skill amazon-opensearch-service

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Amazon OpenSearch Service — the unified skill
2
3	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.
4
5	> 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.
6
7	## Step 0: detect the capability — first thing you do
8
9	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.
10
11	\| Capability \| Entry-point reference \|
12	\|---\|---\|
13	\| migration — Solr / Elasticsearch / self-managed OpenSearch into AOS or AOSS. Schema/query translation, sizing, cutover. \| [`references/assessment-workflow.md`](references/assessment-workflow.md) \|
14	\| provisioning — Provisioning and managing AOS domains and AOSS collections. Lifecycle, upgrades, storage tiers, FGAC, monitoring. \| [`references/provisioning-reference.md`](references/provisioning-reference.md) \|
15	\| search — Vector / semantic / hybrid / sparse / dense / RAG retrieval. Bedrock connectors, FAISS HNSW vs Lucene. \| [`references/search-semantic-search-guide.md`](references/search-semantic-search-guide.md) \|
16	\| log-analytics — Log search, observability, PPL, OSI ingestion, anomaly detection, OpenSearch Dashboards. Splunk/Datadog/ELK alternatives. \| [`references/log-analytics-guide.md`](references/log-analytics-guide.md) \|
17	\| trace-analytics — Distributed traces with OpenTelemetry. Span queries, service maps, Data Prepper. \| [`references/trace-analytics-trace-queries.md`](references/trace-analytics-trace-queries.md) \|
18
19	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.
20
21	## Universal rules (apply to ALL capabilities)
22
23	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.
24
25	- 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.
26	- 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.
27	- No credential leakage (HARD CONSTRAINT). Never include master usernames, KMS key ARNs, VPC endpoint URLs, instance IPs,

People who liked this also viewed

6 picks

Type