Can't hit some endpoints in ES 5.6.2 externally

(Nikolay Klimchuk) #1

I have bizarre problem after installing ES 5.6.2 on AWS EC2 instance for the first time.

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 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.

(David Pilato) #2

Are you using elasticsearch by AWS service by any chance?

(Mark Walkom) #3

Reason being they have a modified Elasticsearch which removes access to a number of core APIs like this one.

(Nikolay Klimchuk) #4

I'm not using AWS ElasticSearch service

(Nikolay Klimchuk) #5

Is there any link describing those changes?

(Mark Walkom) #6

I don't know sorry.

Do you have an IAM role that is protecting this cluster?

(Nikolay Klimchuk) #7

I'm using standard ECS AMI and role.
Another observation:

I can get valid result for http://ip:9200/index_name/_count

But 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.

I can successfully curl both requests from any ES node though
So it's only affecting access from outside of the cluster

(system) #8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.