# Anyone Using AWS ElasticSearch

**URL:** <https://discuss.elastic.co/t/anyone-using-aws-elasticsearch/51510>\
**Category:** Elasticsearch\
**Created:** [June 1, 2016, 4:33am UTC](https://discuss.elastic.co/t/anyone-using-aws-elasticsearch/51510 "2016-06-01T04:33:36Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ninjada](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@ninjada](https://discuss.elastic.co/u/ninjada)\
**Post date:** [June 1, 2016, 4:33am UTC](https://discuss.elastic.co/t/anyone-using-aws-elasticsearch/51510/1 "2016-06-01T04:33:36Z")

</div>

im manually running an ELK cluster (latest versions) on EC2.

just looking at evaluating the elasticsearch service on aws, to see if theres any benefit (less management). i had a brief attempt, but nothing would work only changing the logstash output to the elasticsearch domain address.

is anybody using it? are there any caveats? any setup requirements, like needing any additional plugins or anything?

from reading the docs, it only seems to support up to ES 1.5.3 atm, which seems odd?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 1, 2016, 4:42am UTC](https://discuss.elastic.co/t/anyone-using-aws-elasticsearch/51510/2 "2016-06-01T04:42:39Z")

</div>

They only support 1.5.2 and up to 20 nodes, they have disabled a few of the API end points and don't allow plugins beyond what they provide.

Otherwise I understand it isn't too bad.

---

<div class="post-metadata">

**Author:** ![ninjada](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@ninjada](https://discuss.elastic.co/u/ninjada)\
**Post date:** [June 1, 2016, 5:04am UTC](https://discuss.elastic.co/t/anyone-using-aws-elasticsearch/51510/3 "2016-06-01T05:04:28Z")

</div>

Ahh thats a little disappointing. 1.5.2 seems ancient and no plugin options means I'd need a different backup solution (beyond the duration allowed for a snapshots) to my current s3 weekly index storage via plugins. Or no doubt some expensive AWS data pipeline export solution.

Cheers Mark

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 1, 2016, 5:05am UTC](https://discuss.elastic.co/t/anyone-using-aws-elasticsearch/51510/4 "2016-06-01T05:05:41Z")

</div>

Have you seen [https://www.elastic.co/cloud](https://www.elastic.co/cloud)?

---

<div class="post-metadata">

**Author:** ![ninjada](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@ninjada](https://discuss.elastic.co/u/ninjada)\
**Post date:** [June 1, 2016, 5:10am UTC](https://discuss.elastic.co/t/anyone-using-aws-elasticsearch/51510/5 "2016-06-01T05:10:51Z")

</div>

I have, seems a better option but not quite the one for me costwise until I make a proper business case for multi-region/datacenter coverage. Needs growing, but not quite there yet.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:47pm UTC](https://discuss.elastic.co/t/anyone-using-aws-elasticsearch/51510/6 "2017-07-05T22:47:26Z")

</div>