Another EC2 publish_host public ip problem

Elastic Stack Elasticsearch
1

Hi,

I can't figure out why Elasticsearch still can't be reached from the public
ip of the ec2 instance. This is my config file

cloud.aws.access_key: "AKIAXXXXXXXXXPWEW2A"
cloud.aws.secret_key: "EvU0I5XXXXXXXXXXXXXx+b+FlRXXXSSDFfM2Z"

plugin.mandatory: "cloud-aws"

cluster.name: "escluster"

node.name: "Iron Fist"

discovery.type: "ec2"
discovery.ec2.groups: "launch-wizard-4"
discovery.ec2.host_type: "public_ip"
discovery.ec2.ping_timeout: "30s"
discovery.ec2.availability_zones: "us-east-1a"
cloud.aws.region: "us-east"

discovery.zen.ping.multicast.enabled: false

network.publish_host: "54.31.403.195"

Do you have a hint for me? Curl-ing the private ip works.
Your help is much appreciated.

Thank you, best regards

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/59f12b8d-deef-4c0b-acea-94fcf4237d73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Hi Martin,

Did you check your firewall settings? Did you open 9200 ports so they can be accessible from your local machine?

BTW, those settings are not used. You can comment/remove them:

discovery.zen.ping.multicast.enabled: false
network.publish_host: "54.31.403.195"

--
David Pilato | Technical Advocate | elasticsearch.com
david.pilato@elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 octobre 2014 à 07:40:46, martin.enzinger@gmail.com (martin.enzinger@gmail.com) a écrit:

Hi,

I can't figure out why Elasticsearch still can't be reached from the public ip of the ec2 instance. This is my config file

cloud.aws.access_key: "AKIAXXXXXXXXXPWEW2A"
cloud.aws.secret_key: "EvU0I5XXXXXXXXXXXXXx+b+FlRXXXSSDFfM2Z"

plugin.mandatory: "cloud-aws"

cluster.name: "escluster"

node.name: "Iron Fist"

discovery.type: "ec2"
discovery.ec2.groups: "launch-wizard-4"
discovery.ec2.host_type: "public_ip"
discovery.ec2.ping_timeout: "30s"
discovery.ec2.availability_zones: "us-east-1a"
cloud.aws.region: "us-east"

discovery.zen.ping.multicast.enabled: false

network.publish_host: "54.31.403.195"

Do you have a hint for me? Curl-ing the private ip works.
Your help is much appreciated.

Thank you, best regards

You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/59f12b8d-deef-4c0b-acea-94fcf4237d73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/etPan.5444d4d6.19495cff.8fc%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.