4 ms·
Another point of frustration is that because these endpoints are locked down[0] you cannot fully use management tools like curator - https://github.com/elastic/
by kiernanmcgowan 9y ago
Another point of frustration is that because these endpoints are locked down[0] you cannot fully use management tools like curator - https://github.com/elastic/curator https://github.com/elastic/curator
[0]https://www.elastic.co/guide/en/elasticsearch/client/curator/current/faq_aws_iam.html https://www.elastic.co/guide/en/elasticsearch/client/curator...
- jbyers 9y agoCurator support got better in the AWS ES 5.3 release a few weeks ago: https://github.com/elastic/curator/releases/tag/v5.1.0 https://github.com/elastic/curator/releases/tag/v5.1.0 "AWS ES 5.3 officially supports Curator now. Documentation has been updated to reflect this."
- yissachar 9y agoYou still can't use Curator to take snapshots, because AWS ES doesn't expose the `/_snapshot/_status` endpoint. https://github.com/elastic/curator/issues/639 https://github.com/elastic/curator/issues/639
- coredog64 9y agoIf you are stuck on 5.1.2, the Talend fork of curator works. The change is trivial, so I get the sense that Elastic is just fucking with Amazon.