Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for OpenSearch
  • Getting started
    • Resource relationships
    • Host roles
    • Indexes
    • Index policies
    • Searching with OpenSearch
    • Host classes
    • Networking in Managed Service for OpenSearch
    • Quotas and limits
    • Disk types
    • Backups
    • Sharding and replication
    • OpenSearch plugins
    • OpenSearch versioning policy
    • Maintenance
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ
  1. Concepts
  2. Index policies

Index policies

Written by
Yandex Cloud
Updated at September 9, 2024

A policy is a set of rules that describes how to manage an index. To work with polocies, you can use the OpenSearch Index State Management (ISM) plugin.

In a policy, you define:

  • States an index can be in. You can specify any names for states. Every policy must have at least one state.
  • Actions to perform when an index gets into a certain state. Actions are performed in their given order.
  • Conditions to move an index to a different state (transitions). Transitions are checked in their given order.

For example, you can define a policy that changes your index state to read_only after 30 days and deletes it after 90 days. You can also configure a policy that sends notifications when an index is deleted.

Every policy must have at least one state. Actions and transitions are optional. If you do not specify conditions for a transition, an index is moved to another state by default at the time of verification.

Once a policy is created and attached to an index, the ISM plugin creates a job that checks the conditions for index transitions and performs the policy actions. By default, a job runs every 5 minutes.

For more information about policies, see the OpenSearch documentation.

Was the article helpful?

Previous
Indexes
Next
Searching with OpenSearch
© 2025 Direct Cursus Technology L.L.C.