# Elasticsearch RED status in AWS

**URL:** <https://discuss.elastic.co/t/elasticsearch-red-status-in-aws/45362>\
**Category:** Elasticsearch\
**Created:** [March 24, 2016, 3:42pm UTC](https://discuss.elastic.co/t/elasticsearch-red-status-in-aws/45362 "2016-03-24T15:42:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![irumman](https://avatars.discourse-cdn.com/v4/letter/i/3bc359/32.png) [@irumman](https://discuss.elastic.co/u/irumman)\
**Post date:** [March 24, 2016, 3:42pm UTC](https://discuss.elastic.co/t/elasticsearch-red-status-in-aws/45362/1 "2016-03-24T15:42:45Z")

</div>

Hi,  
I have created an ES domain to search for the vpcglow logs and cloud trail log with daily indexing.  
Right now, the status is RED :

> {  
> "cluster\_name": "678628912247:test",  
> "status": "red",  
> "timed\_out": false,  
> "number\_of\_nodes": 17,  
> "number\_of\_data\_nodes": 17,  
> "active\_primary\_shards": 687,  
> "active\_shards": 1374,  
> "relocating\_shards": 0,  
> "initializing\_shards": 0,  
> "unassigned\_shards": 8,  
> "number\_of\_pending\_tasks": 0  
> }

Further investigating I found, one index is RED:

> red open cwl-2016.02.19 5 1 381700 102899 335.8mb 167.9mb

Looking into the shards:

> cwl-2016.02.19 2 p UNASSIGNED   
> cwl-2016.02.19 2 r UNASSIGNED   
> cwl-2016.02.19 0 p UNASSIGNED   
> cwl-2016.02.19 0 r UNASSIGNED   
> cwl-2016.02.19 3 p STARTED 381700 167.9mb x.x.x.x Elektra Natchios  
> cwl-2016.02.19 3 r STARTED 381700 167.9mb x.x.x.x Chronos   
> cwl-2016.02.19 1 p UNASSIGNED   
> cwl-2016.02.19 1 r UNASSIGNED   
> cwl-2016.02.19 4 p UNASSIGNED   
> cwl-2016.02.19 4 r UNASSIGNED

I tried to reroute the shards to less used nodes, but it gives me:

> {"Message":"Your request: '/\_cluster/reroute' is not allowed."}

Any advice please what I should do now.

Thanks & Regards.

---

<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:** [March 25, 2016, 12:38am UTC](https://discuss.elastic.co/t/elasticsearch-red-status-in-aws/45362/2 "2016-03-25T00:38:17Z")

</div>

> [@irumman](#):
>
> {"Message":"Your request: '/\_cluster/reroute' is not allowed."}

Are you using the AWS ESaaS by chance?

---

<div class="post-metadata">

**Author:** ![irumman](https://avatars.discourse-cdn.com/v4/letter/i/3bc359/32.png) [@irumman](https://discuss.elastic.co/u/irumman)\
**Post date:** [April 4, 2016, 4:09pm UTC](https://discuss.elastic.co/t/elasticsearch-red-status-in-aws/45362/3 "2016-04-04T16:09:52Z")

</div>

Yes. I am. However, I got the status GREEN now. The took the backup of cluster and then deleted RED index.

---

<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:** [April 4, 2016, 9:08pm UTC](https://discuss.elastic.co/t/elasticsearch-red-status-in-aws/45362/4 "2016-04-04T21:08:44Z")

</div>

The AWS service has a number of API limitations in place.

---

<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, 11:02pm UTC](https://discuss.elastic.co/t/elasticsearch-red-status-in-aws/45362/5 "2017-07-05T23:02:29Z")

</div>