Q: Why doesn’t Curator 4 work with AWS Elasticsearch?edit

A: Because Curator 4 requires access to the /_cluster/state/metadata endpoint.edit

There is some confusion because Curator 3 supported AWS ES, but Curator 4 does not. There are even some IAM credentials listed as options for client connections. These are currently available, but not able to be used. This may change at some point, so they remain at the ready until then.

Curator 4 requires access to the /_cluster/state/metadata endpoint in order to pull metadata at IndexList initialization time for all indices. This metadata is used to determine index routing information, index sizing, index state (either open or close), aliases, and more. Curator 4 switched to doing this in order to reduce the number of repetitive client calls that were made in the previous versions.

After Curator 4 was released, AWS announced it’s 2.3 version of Elasticsearch. Unfortunately, this version did not support the /_cluster/state/metadata endpoint, which means that Curator cannot be used to manage indices in AWS.

This thread (requires AWS login credentials) tracks the issue on the Amazon side.