# Easy EC2 configuration question **URL:** \ **Category:** Elasticsearch\ **Created:** [February 14, 2011, 7:59pm UTC](https://discuss.elastic.co/t/easy-ec2-configuration-question/3929 "2011-02-14T19:59:23Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![flowdave](https://avatars.discourse-cdn.com/v4/letter/f/5f9b8f/32.png) [@flowdave](https://discuss.elastic.co/u/flowdave)\ **Post date:** [February 14, 2011, 7:59pm UTC](https://discuss.elastic.co/t/easy-ec2-configuration-question/3929/1 "2011-02-14T19:59:23Z")
Hello List. I am obviously doing something very wrong, but after two days of poking at the configuration, I thought it might be more efficacious to ask the list. I currently have two amazon EC2 instances dedicated to ES, both running Ubuntu 10.10. I have this minimal configuration in elasticsearch.yml - cloud: aws: access\_key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXj ``` secret_key: XXXXXXXXXXXXXXXXXX ``` the machines are named esearch\_1 and esearch\_2 (I mention just in passing) Here is what I see when I run ES on each machine. Notice that neither machine sees the other: root@esearch\_1:~$/mnt/flow/elasticsearch-0.14.4/bin/elasticsearch -f [2011-02-14 19:50:20,347][INFO][node] [Hephaestus] {elasticsearch/0.14.4}[3161]: initializing ... [2011-02-14 19:50:20,442][INFO][plugins] [Hephaestus] loaded [] [2011-02-14 19:50:23,995][INFO][node] [Hephaestus] {elasticsearch/0.14.4}[3161]: initialized [2011-02-14 19:50:23,995][INFO][node] [Hephaestus] {elasticsearch/0.14.4}[3161]: starting ... [2011-02-14 19:50:24,181][INFO][transport] [Hephaestus] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/10.114.95.22:9300]} [2011-02-14 19:50:27,285][INFO][cluster.service] [Hephaestus] new\_master [Hephaestus][E4425jmERGy-JJAfUoi-GA][inet[/10.114.95.22:9300]], reason: zen-disco-join (elected\_as\_master) [2011-02-14 19:50:27,417][INFO][discovery] [Hephaestus] elasticsearch/E4425jmERGy-JJAfUoi-GA [2011-02-14 19:50:27,434][INFO][http] [Hephaestus] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/10.114.95.22:9200]} [2011-02-14 19:50:27,435][INFO][node] [Hephaestus] {elasticsearch/0.14.4}[3161]: started root@esearch\_2:~$/mnt/flow/elasticsearch-0.14.4/bin/elasticsearch -f [2011-02-14 19:49:11,978][INFO][node] [Aero] {elasticsearch/0.14.4}[18844]: initializing ... [2011-02-14 19:49:11,981][INFO][plugins] [Aero] loaded [] [2011-02-14 19:49:15,777][INFO][node] [Aero] {elasticsearch/0.14.4}[18844]: initialized [2011-02-14 19:49:15,778][INFO][node] [Aero] {elasticsearch/0.14.4}[18844]: starting ... [2011-02-14 19:49:15,935][INFO][transport] [Aero] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/10.243.46.209:9300]} [2011-02-14 19:49:19,137][INFO][cluster.service] [Aero] new\_master [Aero][ax2BL-VlSkOU31zdlOriKg][inet[/10.243.46.209:9300]], reason: zen-disco-join (elected\_as\_master) [2011-02-14 19:49:19,244][INFO][discovery] [Aero] elasticsearch/ax2BL-VlSkOU31zdlOriKg [2011-02-14 19:49:19,410][INFO][http] [Aero] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/10.243.46.209:9200]} [2011-02-14 19:49:19,410][INFO][node] [Aero] {elasticsearch/0.14.4}[18844]: started Please notice that both machines decide to be a master: e.g. - new\_master [Hephaestus][E4425jmERGy-JJAfUoi-GA][inet[/10.114.95.22:9300]], reason: zen-disco-join (elected\_as\_master) Obviously I have mangled the configuration somehow, but after trying several different things, I am at a loss. Thank you for any configuration help you can provide! Regards, Dave Kirkpatrick ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:12am UTC](https://discuss.elastic.co/t/easy-ec2-configuration-question/3929/2 "2017-07-06T04:12:04Z")
Closed on July 6, 2017, 4:12am UTC