How to configure OpenSearch ISM hot-warm-cold architecture
Design the hot, warm, cold and frozen tiers and wire an index to each with explicit routing attributes.
Production-grade guidance for designing index lifecycle policies, automating rollovers, routing data across hot–warm–cold tiers, and replicating indices across clusters — built for the engineers who keep search and logging platforms reliable.
OpenSearch Index State Management turns retention, performance, and cost requirements into a deterministic state machine. This resource explains how that machine works — from policy evaluation and node-role allocation to rollover triggers and Cross-Cluster Replication — and pairs each concept with copy-ready configuration and Python automation.
Everything here is oriented toward production: explicit routing attributes, idempotent policy attachment, safe threshold tuning, and graceful fallback when nodes fail. Use it as a reference while you build, or as a troubleshooting companion when transitions get stuck.
New to OpenSearch ISM? These hands-on guides are the fastest way in — each one pairs the concept with copy-ready configuration and Python you can run against a real cluster.
Design the hot, warm, cold and frozen tiers and wire an index to each with explicit routing attributes.
Map Elasticsearch ILM phases to ISM states — a feature-parity reference for teams migrating.
Force deterministic rollovers from Python the moment a hot index crosses its size threshold.
Treat ISM policy JSON as code: validate, diff and apply it through a gated deployment pipeline.
Connect a follower to its leader, bootstrap replication, and watch it reach a synced state.
Keep a single writer during a network partition and fail over without diverging your data.
OpenSearch Index State Management (ISM) is a policy-driven state machine that automates index rollover, tiered shard allocation, segment optimization, snapshotting, and deletion...
OpenSearch Index State Management (ISM) turns index lifecycle — rollover, tiered allocation, force-merge, snapshot, and deletion — into a declarative state machine that an...
OpenSearch Cross-Cluster Replication (CCR) continuously ships index operations from a leader cluster to one or more read-only follower clusters, giving you an active-passive...