# Reindexing with logstash in AWS ES service

**URL:** <https://discuss.elastic.co/t/reindexing-with-logstash-in-aws-es-service/35856>\
**Category:** Elasticsearch\
**Created:** [November 30, 2015, 2:51am UTC](https://discuss.elastic.co/t/reindexing-with-logstash-in-aws-es-service/35856 "2015-11-30T02:51:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![James\_Tang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james_tang/32/8112_2.png) [@James\_Tang](https://discuss.elastic.co/u/James_Tang)\
**Post date:** [February 26, 2016, 6:38am UTC](https://discuss.elastic.co/t/reindexing-with-logstash-in-aws-es-service/35856/3 "2016-02-26T06:38:22Z")

</div>

Faced the same issue with you. But managed to worked around the issue. The best solution is basically to upgrade the to a bigger, better machine. Use the paramedic plugin to view the utilization. I give you my example.

How I approach it: [Logstash Reindex Strategy](https://discuss.elastic.co/t/logstash-reindex-strategy/42812)

---

_[View the full topic](https://discuss.elastic.co/t/reindexing-with-logstash-in-aws-es-service/35856)._