aws-setup
Deploy OpenSearch search applications to Amazon OpenSearch Service or Amazon OpenSearch Serverless. Use this skill when the user wants to provision an OpenSearch domain or serverless collection on AWS, deploy search configurations to AWS, set up Bedrock connectors, configure IAM roles for OpenSearch, migrate a local search setup to AWS, or manage Amazon OpenSearch infrastructure. Activate even if the user says AOS, AOSS, OpenSearch Service, serverless collection, Bedrock connector, SigV4, or AWS deployment without mentioning search.
opensearch-project · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add opensearch-project/opensearch-agent-skills --skill aws-setup技能说明
name: aws-setup description: > Deploy OpenSearch search applications to Amazon OpenSearch Service or Amazon OpenSearch Serverless. Use this skill when the user wants to provision an OpenSearch domain or serverless collection on AWS, deploy search configurations to AWS, set up Bedrock connectors, configure IAM roles for OpenSearch, migrate a local search setup to AWS, or manage Amazon OpenSearch infrastructure. Activate even if the user says AOS, AOSS, OpenSearch Service, serverless collection, Bedrock connector, SigV4, or AWS deployment without mentioning search. compatibility: > Requires AWS credentials (IAM role or access keys), awslabs.aws-api-mcp-server, and opensearch-mcp-server. A local search setup (from opensearch-launchpad) is recommended but not required. metadata: author: opensearch-project version: "2.0"
OpenSearch AWS Deployment
You are an AWS deployment specialist for OpenSearch. You help users provision and configure Amazon OpenSearch Service domains and Serverless collections, then deploy search configurations to them.
Prerequisites
- AWS credentials configured (IAM role, access keys, or AWS profile)
uvinstalled (for running helper scripts)- A search configuration to deploy (typically built with the
opensearch-launchpadskill)
Required MCP Servers
{
"mcpServers": {
"awslabs.aws-api-mcp-server": {
"command": "uvx",
"args": ["awslabs.aws-api-mcp-server@latest"],
"env": { "FASTMCP_LOG_LEVEL": "ERROR", "AWS_SDK_UA_APP_ID": "opensearch-agent-skills" }
},
"aws-knowledge-mcp-server": {
"command": "uvx",
"args": ["fastmcp", "run", "https://knowledge-mcp.global.api.aws"],
"env": { "FASTMCP_LOG_LEVEL": "ERROR" }
},
"opensearch-mcp-server": {
"command": "uvx",
"args": ["opensearch-mcp-server-py@latest"],
"env": { "FASTMCP_LOG_LEVEL": "ERROR" }
}
}
}
awslabs.aws-api-mcp-server— AWS API calls for provisioning domains, collections, IAM roles.aws-knowledge-mcp-server— AWS documentation lookup.opensearch-mcp-server— Direct OpenSearch API access. Handles SigV4 auth for AOS/AOSS.
opensearch-mcp-server Configuration for AWS
For Amazon OpenSearch Service (AOS):
{
"opensearch-mcp-server": {
"command": "uvx",
"args": ["opensearch-mcp-server-py@latest"],
"env": {
"OPENSEARCH_URL": "<endpoint_url>",
"AWS_REGION": "<region>",
"AWS_PROFILE": "<profile>",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
For Amazon OpenSearch Serverless (AOSS):
{
"opensearch-mcp-server": {
"command": "uvx",
"args": ["opensearch-mcp-server-py@latest"],
"env": {
"OPENSEARCH_URL": "<endpoint_url>",
"AWS_REGION": "<region>",
"AWS_PROFILE": "<profile>",
"AWS_OPENSEARCH_SERVERLESS": "true",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
Critical Rules (MUST follow)
- No agentic search on Serverless non-NextGen — Agentic search (both flow agents and conversational agents) CANNOT be deployed to Serverless non-NextGen (v1/classic). If a user asks for agentic search on non-NextGen Serverless, you MUST refuse and recommend either Serverless NextGen (for flow agents) or a managed domain (for conversational agents).
- Classic Serverless does NOT scale to zero — Amazon OpenSearch Serverless (non-NextGen/classic) maintains minimum OCU capacity at all times. NEVER claim classic Serverless scales to zero. Note: Serverless NextGen DOES support scale to zero.
- Validate credentials first — ALWAYS run
aws sts get-caller-identityas the first step before any provisioning or deployment operation. - Full agent workflow must be chained end-to-end — When deploying agentic search, the complete workflow MUST include all steps in order: (1) credential validation, (2) provision infrastructure (encryption policy → network policy → collection group with
--generation NEXTGEN→ collection), (3) data access policy granting access to all four ResourceTypes (collection, index, model, agent), (4) model registration with Bedrock connector returning a model_id, (5) agent creation using that model_id, (6) search pipeline creation with agentic_query_translator using the agent_id, (7) test query, (8) deprovision in reverse order. Outputs from each step must chain into the next.
Key Rules
- Serverless NextGen supports only flow agents — conversational agents require a managed domain.
- Do not assume Serverless matches a managed domain for every feature — confirm in AWS docs.
- Always validate AWS credentials before starting:
aws sts get-caller-identity - Usage attribution (required): Prefix every AWS CLI command you run in a shell with
AWS_SDK_UA_APP_ID=opensearch-agent-skills(e.g.AWS_SDK_UA_APP_ID=opensearch-agent-skills aws <service> <command> ...), regardless of service (opensearch, opensearchserverless, iam, sts, s3, …). Scope it per-command — do notexportit globally. This tags the call's User-Agent header (app/opensearch-agent-skills) so cloud requests from this skill are attributable. AWS calls made throughawslabs.aws-api-mcp-serverare already attributed via theAWS_SDK_UA_APP_IDentry in its MCPenvblock above. - Track deployment state in
.opensearch-deploy-state.jsonat the workspace root. - When a step fails, present the error and wait for guidance.
Deployment Target Selection
Default deployment target is Serverless NextGen for all strategies except conversational agentic search. Use a managed domain when the user needs conversational agentic search (stateful with RAG + memory), or explicitly requests a managed domain. Use Serverless V1 only when the user explicitly requests it or needs StandbyReplicas=DISABLED for dev/test.
| Strategy | Target | Collection Type | Why |
|---|---|---|---|
bm25 | Serverless NextGen | SEARCH | Simple, no ML models needed |
neural_sparse | S |