# Can't hit some endpoints in ES 5.6.2 externally **URL:** \ **Category:** Elasticsearch\ **Created:** [October 5, 2017, 7:13pm UTC](https://discuss.elastic.co/t/cant-hit-some-endpoints-in-es-5-6-2-externally/102897 "2017-10-05T19:13:26Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Nikolay\_Klimchuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolay_klimchuk/32/2131_2.png) [@Nikolay\_Klimchuk](https://discuss.elastic.co/u/Nikolay_Klimchuk)\ **Post date:** [October 5, 2017, 7:13pm UTC](https://discuss.elastic.co/t/cant-hit-some-endpoints-in-es-5-6-2-externally/102897/1 "2017-10-05T19:13:26Z")
I have bizarre problem after installing ES 5.6.2 on AWS EC2 instance for the first time. Request: [http://34.207.177.92:9200/\_cluster](http://34.207.177.92:9200/_cluster) Response: {"error":{"root\_cause":[{"type":"illegal\_argument\_exception","reason":"No endpoint or operation is available at [\_cluster]"}],"type":"illegal\_argument\_exception","reason":"No endpoint or operation is available at [\_cluster]"},"status":400} When I'm calling ES from EC2 instance itself I'm getting valid JSON data Interestingly some requests like [http://34.207.177.92:9200/\_count](http://34.207.177.92:9200/_count) working externally with no problems Spent couple hours searching in Google and still can't figure out what makes \_cluster endpoint disappear for external clients. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 5, 2017, 9:56pm UTC](https://discuss.elastic.co/t/cant-hit-some-endpoints-in-es-5-6-2-externally/102897/2 "2017-10-05T21:56:38Z")
Are you using elasticsearch by AWS service by any chance? ---
**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:** [October 5, 2017, 11:27pm UTC](https://discuss.elastic.co/t/cant-hit-some-endpoints-in-es-5-6-2-externally/102897/3 "2017-10-05T23:27:04Z")
> [@dadoonet](#): > > Are you using elasticsearch by AWS service by any chance? Reason being they have a modified Elasticsearch which removes access to a number of core APIs like this one. ---
**Author:** ![Nikolay\_Klimchuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolay_klimchuk/32/2131_2.png) [@Nikolay\_Klimchuk](https://discuss.elastic.co/u/Nikolay_Klimchuk)\ **Post date:** [October 6, 2017, 2:25pm UTC](https://discuss.elastic.co/t/cant-hit-some-endpoints-in-es-5-6-2-externally/102897/4 "2017-10-06T14:25:07Z")
I'm not using AWS ElasticSearch service ---
**Author:** ![Nikolay\_Klimchuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolay_klimchuk/32/2131_2.png) [@Nikolay\_Klimchuk](https://discuss.elastic.co/u/Nikolay_Klimchuk)\ **Post date:** [October 6, 2017, 2:25pm UTC](https://discuss.elastic.co/t/cant-hit-some-endpoints-in-es-5-6-2-externally/102897/5 "2017-10-06T14:25:28Z")
Is there any link describing those changes? Thanks! ---
**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:** [October 6, 2017, 8:27pm UTC](https://discuss.elastic.co/t/cant-hit-some-endpoints-in-es-5-6-2-externally/102897/6 "2017-10-06T20:27:19Z")
I don't know sorry. Do you have an IAM role that is protecting this cluster? ---
**Author:** ![Nikolay\_Klimchuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolay_klimchuk/32/2131_2.png) [@Nikolay\_Klimchuk](https://discuss.elastic.co/u/Nikolay_Klimchuk)\ **Post date:** [October 10, 2017, 4:40pm UTC](https://discuss.elastic.co/t/cant-hit-some-endpoints-in-es-5-6-2-externally/102897/7 "2017-10-10T16:40:25Z")
I'm using standard ECS AMI and role. Another observation: I can get valid result for [http://ip:9200/index\_name/\_count](http://ip:9200/index_name/_count) {"count":1,"\_shards":{"total":1,"successful":1,"skipped":0,"failed":0}} But [http://ip:9200/index\_name/\_search?q=whatever](http://ip:9200/index_name/_search?q=whatever) failes because ES doesn't return anything at all Browser says The connection to the website was reset. Error Code: INET\_E\_DOWNLOAD\_FAILURE I can successfully curl both requests from any ES node though So it's only affecting access from outside of the cluster ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 7, 2017, 4:40pm UTC](https://discuss.elastic.co/t/cant-hit-some-endpoints-in-es-5-6-2-externally/102897/8 "2017-11-07T16:40:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.