Need help with curator?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

2.8K Stars 615 Forks Other 1.6K Commits 159 Opened issues


Curator: Tending your Elasticsearch indices

Services available


Need anything else?

Contributors list

.. _readme:


Have indices in Elasticsearch? This is the tool for you!

Like a museum curator manages the exhibits and collections on display, Elasticsearch Curator helps you curate, or manage your indices.

Build Status

+--------+----------+ | Branch | Status | +========+==========+ | Master | |master| | +--------+----------+ | 5.x | |5_x| | +--------+----------+

PyPI: |pypi_pkg|

.. |master| image:: :target: .. |5x| image:: :target: .. |pypipkg| image:: :target:

Curator API Documentation

Curator ships with both an API and a wrapper script (which is actually defined as an entry point). The API allows you to write your own scripts to accomplish similar goals, or even new and different things with the

Curator API
, and the
Elasticsearch Python API

.. _Curator API:

.. Curator API Documentation:

Curator API

.. _Elasticsearch Python API:

Curator CLI Documentation


Curator CLI Documentation
_ is now a part of the document repository at at

.. _Curator CLI Documentation:

Getting Started

.. _Getting Started:

See the

Installation guide 
_ and the
command-line usage guide 


curator --help
will also show usage information.


  • fork the repo
  • make changes in your fork
  • add tests to cover your changes (if necessary)
  • run tests
  • sign the
  • send a pull request!

To run from source, use the
script in the root directory of the project.

Running Tests

To run the test suite just run

python test

When changing code, contributing new code or fixing a bug please make sure you include tests in your PR (or mark it as without tests so that someone else can pick it up to add the tests). When fixing a bug please make sure the test actually tests the bug - it should fail without the code changes and pass after they're applied (it can still be one commit of course).

The tests will try to connect to your local elasticsearch instance and run integration tests against it. This will delete all the data stored there! You can use the env variable

to point to a different instance (for example, 'otherhost:9203').


Curator was first called
[1] and was almost immediately renamed to
[1]. After a time it was migrated under the logstash repository as
. Soon thereafter, Jordan Sissel was hired by Elasticsearch, as was the original author of this tool. It became Elasticsearch Curator after that and is now hosted at


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.