# Ec2-discovery issues with Kibana host **URL:** \ **Category:** Elasticsearch\ **Created:** [July 9, 2018, 10:49am UTC](https://discuss.elastic.co/t/ec2-discovery-issues-with-kibana-host/139143 "2018-07-09T10:49:42Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![tomerl](https://avatars.discourse-cdn.com/v4/letter/t/7ab992/32.png) [@tomerl](https://discuss.elastic.co/u/tomerl)\ **Post date:** [July 9, 2018, 10:49am UTC](https://discuss.elastic.co/t/ec2-discovery-issues-with-kibana-host/139143/1 "2018-07-09T10:49:42Z")
Hi, I've created a cluster of 3 ES 6.3 nodes on AWS: 2 nodes acts as master and data and 1 node serves as the coordinated server with Kibana installed. My elasticsearch.yml is configured with the ec2-discovery: network.host: _ec2_ cluster.name: elk-dev plugin.mandatory: discovery-ec2 discovery.zen.hosts\_provider: ec2 discovery.ec2.groups: sg-8e4c89f2 discovery.ec2.host\_type: private\_ip discovery.ec2.tag.Cluster: default-elk-dev discovery.ec2.availability\_zones: eu-west-1a,eu-west-1b,eu-west-1c discovery.ec2.endpoint: [ec2.eu-west-1.amazonaws.com](http://ec2.eu-west-1.amazonaws.com) discovery.ec2.protocol: http When I connect to Kibana board, I can see error "unable to connect to [http://localhost:9200](http://localhost:9200)". Since _ec2_ does not resolve to 127.0.0.1 but to the private IP it obviously fails unless I change the network.host to 0.0.0.0 which eventually works. How can I keep using _ec2_ as network.host instead of changing it to 0.0.0.0? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 6, 2018, 10:49am UTC](https://discuss.elastic.co/t/ec2-discovery-issues-with-kibana-host/139143/2 "2018-08-06T10:49:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.