ElasticSearch install on AWS - unable to connect on public ip/host

Question

I have an single EC2 CentOS instance with ElasticSearch installed.

I am unable to connect externally using the public ip or hostname.

ElasticSearch starts correctly and I can access locally on the machine using:

CURL <my_internal_ip>:9200

However running the same remotely using the public ip fails.

I have the the cloud-aws plugin is installed
I have setup an AWS security group with all tcp ports open for testing

I am guessing I need to bind the address within the elasticsearch.yml file, however do not understand which setting to use, and with what address. Setting the network.host to an external address stops ES from starting - unable to bind.

Appreciate any comments.

score 0 · Answer 1 · answered Nov 25 '13 at 07:59

0

Amazon Ec2 Instance is use remotely according with the Elastic Search Installed that provide the aws cloud plugins

answered Nov 25 '13 at 07:59

Jhon Calton

9
2

Im not sure I understand your comment. Can you clarify? – Ben Nov 25 '13 at 10:10
Amazon Ec2 instance use according for elastic search installation – Jhon Calton Dec 05 '13 at 11:55

score 0 · Accepted Answer · answered Nov 25 '13 at 17:25

0

After many hours....

IP Tables was enabled on the OS as default blocking my elasticsearch ports.

answered Nov 25 '13 at 17:25

Ben

6,026
11
51
72

score 0 · Answer 3 · edited Oct 24 '18 at 02:58

0

I've the same issue and followed below steps and get resolved: Elasticsearch process memory locking failed

MAX_LOCKED_MEMORY=unlimited
LimitMEMLOCK=infinity

Do these two steps also.

edited Oct 24 '18 at 02:58

Nisse Engström

4,738
23
27
42

answered Oct 24 '18 at 02:29

vish

671
2
7
15

ElasticSearch install on AWS - unable to connect on public ip/host

3 Answers3