What problem does it solve? Working with a managed Amazon OpenSearch Service domain requires SigV4 request signing, IAM access-policy knowledge, and careful handling of destructive operations like reindexing or index deletion. This Skill provides a signed client and operational playbook so you can inspect cluster health, search indices, fix red/yellow clusters, and manage dashboards without hand-signing curl requests or risking unreviewed destructive changes. ## Core Features & Use Cases - SigV4-signed client: A Python helper script handles credential resolution, request signing, and JSON handling for every call to an es.amazonaws.com endpoint. - Read and diagnose: Check cluster health, list indices, inspect mappings and settings, run searches and counts, and explain unassigned shards. - Safe remediation: Reindex, edit mappings and settings, manage ISM policies and snapshots, and run update/delete-by-query — all dry-run by default with an explicit --confirm gate. - Dashboards management: Export, edit, and import OpenSearch Dashboards saved objects as NDJSON across domains and tenants. - Use Case: Your logs cluster turns yellow after a node change. Run the allocation command to see why shards are unassigned, retry failed allocations, and reduce replica counts on legacy indices — all with dry-run previews before anything changes. ## Quick Start Ask the assistant to check the health of your OpenSearch domain and list any unassigned shards, providing your domain endpoint and AWS region.