Accessing ElasticSearch on EC2 instance from outside the cloud

Question

I am trying to access my ElasticSearch on a running EC2 instance from outside the Cloud. I currently have SSH/HTTP/HTTPS open to the public for inbound traffic as well as all open for outbound traffic. I set up a public IP for my EC2 instance as well.

By default ElasticSearch is on port 9200. I'm not sure if I configured my elasticsearch.yml file correctly but it basically has the default configuration I only changed the cluster.name to something else.

When I type in my public IP with port 9200 into my local browser or locally do a telnet {public-ip} 9200, there is no response. When I SSH into my EC2 instance. I can perform a curl localhost:9200 and I get the correct response from elasticsearch

How can I connect to my ElasticSearch running on my EC2 instance from outside the cloud?

I added a Custom Rule for my security group for inbound traffic that includes port 9200 and is open to 0.0.0.0/0 and I still cannot access this EC2 instance

@error2007s something like this? https://postimg.org/image/gos753jyp/ — Liondancer, Sep 07 '16 at 00:29
Yes add that security rule and then try if you are able to connect. — Piyush Patil, Sep 07 '16 at 00:30
@error2007s tried my public-ip:9200 on my browser and got `Site cannot be reached` =[ Same for `telnet` as well — Liondancer, Sep 07 '16 at 00:34

score 2 · Answer 1 · answered Sep 25 '16 at 16:22

Potential issues to check are wrong binding and instance operating system firewall.

Check where elasticsearch is binding, as if it is binding to 127.0.0.1 you won't be able to reach it from the outside.

Check binding by running in one shell on the elasticsearch ec2:

sudo netstat -lptun | grep 9200

If it shows 127.0.0.1:9200 then there is a misconfiguration if otherwise shows *:9200 or :9200 then it is correct.

If it shows 127.0.0.1 then you should modify elasticsearch parameter network.bind_host as described in:https://www.elastic.co/guide/en/elasticsearch/reference/1.4/modules-network.html

Additionally http/HTTPS and ssh are usually allowed by default operating system firewall, whereas elasticsearch 9200 is not. This is usually the case for rhel and centos. You can temporarily disable iptables and check if it works.

To disable iptables run:

sudo iptables -F

If after disabling iptables the connection works you should configure iptables to allow connection on 9200.

I hope this helps.

G.

D. Soloviev · Answer 2 · 2016-09-07T11:36:51.560

-1

It is mess around Security Groups

You can add or remove rules for a security group (also referred to as authorizing or revoking inbound or outbound access).

You shuld use the SG while launching your instance whith bounded 9200

edited Sep 07 '16 at 11:36

answered Sep 07 '16 at 00:26

D. Soloviev

19
3

While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - [From Review](/review/low-quality-posts/13591734) – Nikolay Mihaylov Sep 07 '16 at 06:57
@Liondancer yes, thats it – D. Soloviev Sep 07 '16 at 11:38
@NikolayMihaylov is it OK now? – D. Soloviev Sep 07 '16 at 11:41

score -1 · Answer 3 · answered Aug 14 '19 at 18:27

-1

Establish an SSH tunnel from your desktop to EC2.. then simply use your browser.. follow steps as given in https://www.jeremydaly.com/access-aws-vpc-based-elasticsearch-cluster-locally/

answered Aug 14 '19 at 18:27

Apurva Singh

4,534
4
33
42

Accessing ElasticSearch on EC2 instance from outside the cloud

3 Answers3