# Curator 2.0 fails

**URL:** <https://discuss.elastic.co/t/curator-2-0-fails/35194>\
**Category:** Elasticsearch\
**Created:** [November 20, 2015, 11:58pm UTC](https://discuss.elastic.co/t/curator-2-0-fails/35194 "2015-11-20T23:58:57Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![bluethundr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bluethundr/32/409_2.png) [@bluethundr](https://discuss.elastic.co/u/bluethundr)\
**Post date:** [November 21, 2015, 12:48am UTC](https://discuss.elastic.co/t/curator-2-0-fails/35194/3 "2015-11-21T00:48:46Z")

</div>

> [@theuntergeek](#):
>
> You should be using Curator 3.4.0, which is what the documentation linked is referencing. 2.0 is very old, and before a major API change, which is reflected in the docs you linked.

Ahhh! Thanks Aaron! I guess I didn't read down far enough into that page.

Working just fine at this point:

```
root@logs:~] #curator --http_auth admin:$ES_PASS show indices --all-indices
2015-11-20 19:44:11,598 INFO Job starting: show indices
2015-11-20 19:44:11,614 INFO Matching all indices. Ignoring flags other than --exclude.
2015-11-20 19:44:11,614 INFO Action show will be performed on the following indices: [u'.kibana', u'logstash-2015.11.19', u'logstash-2015.11.21']
2015-11-20 19:44:11,614 INFO Matching indices:
.kibana
logstash-2015.11.19
logstash-2015.11.21

```

I appreciate the input!

Also, I hate to bring this up, but I am still stuck with a bigger issue of getting LS to write to ES+Shield, using ES 2.0. I had this working fine under ES 1.7.1. But since the upgrade, no joy! Also, LS works beautifully minus shield! But I don't want to leave my ES cluster exposed.

Could I get your input on this issue?

[LS fails to write to ES + Shield](https://discuss.elastic.co/t/ls-cant-connect-to-es-with-shield/34756/8)

Thanks!

---

_[View the full topic](https://discuss.elastic.co/t/curator-2-0-fails/35194)._