AOSREL04-BP02 Implement an Index State Management (ISM) policy to generate snapshots for your crucial indices
Protect your critical Amazon OpenSearch Service indices by implementing an ISM policy that generates snapshots for disaster recovery, which helps you comply with regulatory requirements and simplify the recovery process.
Level of risk exposed if this best practice is not established: High
Desired outcome: Your crucial indices are protected by an ISM policy that generates snapshots for disaster recovery.
Benefits of establishing this best practice: By establishing a manual snapshot repository and using ISM and SM, you maintain full control over your Amazon OpenSearch Service data, and you can comply with regulatory requirements and data retention policies. Additionally, it can simplify disaster recovery processes by having a centralized repository for snapshots.
Implementation guidance
ISM automates index lifecycle tasks, including alias rollovers, snapshots, storage tier transitions, and deletion of old indices.
It is recommended that you review AOSPERF01 and AOSPERF02 to familiarize yourself with sharding strategies before you implement ISM policies.
Additionally, consult
Index
State Management in Amazon OpenSearch Service,
Tutorial:
Automating Index State Management processes and
Index
State Management
Implementation steps
-
Open OpenSearch Dashboards for your domain.
-
From the left sidebar, select Index Management, then Create policy.
-
Use the visual editor
or JSON editor to create policies. We recommend using the visual editor as it offers a more structured way of defining policies. -
After you create a policy, attach it to one or more indexes:
POST _plugins/_ism/add/my-index { "policy_id": "my-policy-id" }
Resources
