Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 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
    • Storage
    • 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 November 26, 2025

A policy is a set of rules that describes how to manage an index. You can work with policies using the OpenSearch Index State Management (ISM) plugin.

In a policy, you define:

  • States the index can be in. You can name states according to your preference. Each policy must have at least one state.

  • Actions to perform when the index enters a particular state. Actions are performed in the order they are listed.

    In Managed Service for OpenSearch, in addition to standard OpenSearch actions, you can also modify the index codec.

  • Transitions are conditions for the index to switch to a different state. Transitions are checked in the order they are listed.

For example, you can set up a policy that will make the index read_only in 30 days and delete it in 90 days. You can also configure a policy that notifies you when the index is deleted.

Each policy must have at least one state. Actions and transitions are optional. If no transition conditions are specified, the index will switch states unconditionally the moment the check takes place.

Once a policy is created and linked to the index, the ISM plugin creates a job that checks the index transition conditions and performs the policy actions. By default, the job is performed every 5 minutes.

For more information about policies, see the OpenSearch documentation.

Use casesUse cases

  • Configuring an index policy in Managed Service for OpenSearch

Was the article helpful?

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