# Cloud AWS plugin intermittent problem ES 1.7 AWS plugin 2.7.1 **URL:** \ **Category:** Elasticsearch\ **Created:** [August 1, 2016, 1:08pm UTC](https://discuss.elastic.co/t/cloud-aws-plugin-intermittent-problem-es-1-7-aws-plugin-2-7-1/56891 "2016-08-01T13:08:53Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![bvoros](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bvoros/32/5246_2.png) [@bvoros](https://discuss.elastic.co/u/bvoros)\ **Post date:** [August 1, 2016, 1:08pm UTC](https://discuss.elastic.co/t/cloud-aws-plugin-intermittent-problem-es-1-7-aws-plugin-2-7-1/56891/1 "2016-08-01T13:08:53Z")
Hello All, I am using the AWS plugin (ver 2.7.1) with ES 1.7.5 in Amazon for cluster discovery. All is well most of the time. Sometimes however it simply does not work and and there is no indication why. Scenario 1. New cluster is launched using a script, the instances get the relevant role assigned. When the cluster stands up, you get 503. Then these instances are terminated, and the cluster is launched again using the same script. Second/Third time the cluster comes up and all is well. No changes made. Sometimes this succeeds the first time. Scenario 2. A change was made to elasticsearch.yml on each node of a running cluster. The cluster was launched with the script mentioned above. After having restarted each node one by one while keeping an eye on cluster status. One node is just unable to discover the rest of the cluster using the AWS plugin. Again, this is a node that was joined into this cluster using the plugin before. Has anyone come across this before? Thanks in advance, Extarct from the log: [2016-08-01 12:27:52,888][INFO][node] [ip-10-20-xxx-xxx] initializing ... **[2016-08-01 12:27:53,055][INFO][plugins] [ip-10-20-xxx-xxx] loaded [cloud-aws], sites []** [2016-08-01 12:27:53,107][INFO][env] [ip-10-20-xxx-xxx] using [1] data paths, mounts [[/ (/dev/xvda1)]], net usable\_space [119.1gb], net total\_space [125.8gb], types [ext4] [2016-08-01 12:27:56,716][INFO][node] [ip-10-20-xxx-xxx] initialized [2016-08-01 12:27:56,716][INFO][node] [ip-10-20-xxx-xxx] starting ... [2016-08-01 12:27:56,842][INFO][transport] [ip-10-20-xxx-xxx] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/10.20.xxx.xxx:9300]} [2016-08-01 12:27:56,899][INFO][discovery] [ip-10-20-xxx-xxx] thisEsCluster/HOO-XTFrSduT5uirb-xBGA [2016-08-01 12:28:26,899][WARN][discovery] [ip-10-20-xxx-xxx] waited for 30s and no initial state was set by the discovery [2016-08-01 12:28:26,904][INFO][http] [ip-10-20-xxx-xxx] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/10.20.xxx.xxx:9200]} [2016-08-01 12:28:26,904][INFO][node] [ip-10-20-xxx-xxx] started **[2016-08-01 12:39:53,738][DEBUG][action.admin.cluster.health] [ip-10-20-xxx-xxx] no known master node, scheduling a retry** **[2016-08-01 12:40:23,740][DEBUG][action.admin.cluster.health] [ip-10-20-xxx-xxx] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]** [2016-08-01 12:40:23,934][DEBUG][action.admin.indices.get] [ip-10-20-xxx-xxx] no known master node, scheduling a retry [2016-08-01 12:40:53,934][DEBUG][action.admin.indices.get] [ip-10-20-xxx-xxx] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s] ---
**Author:** ![bvoros](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bvoros/32/5246_2.png) [@bvoros](https://discuss.elastic.co/u/bvoros)\ **Post date:** [August 2, 2016, 12:04pm UTC](https://discuss.elastic.co/t/cloud-aws-plugin-intermittent-problem-es-1-7-aws-plugin-2-7-1/56891/2 "2016-08-02T12:04:51Z")
Found the cause of the problem. Typo, as always. The discovery statements in my elasticsearch.yml were missing the ec2 bit. As a result, discovery was running with default values which worked in AWS EU but not in Oregon. Incorrect yml: bootstrap.mlockall: true discovery.zen.ping.multicast.enabled: false [cluster.name](http://cluster.name): thisEsCluster [node.name](http://node.name): ${HOSTNAME} cloud.aws.region: eu-west discovery.type: ec2 discovery.groups: elasticsearchCluster discovery.ping\_timeout: 60s cloud.node.auto\_attributes: true discovery.zen.minimum\_master\_nodes: 2 Correct yml: bootstrap.mlockall: true discovery.zen.ping.multicast.enabled: false [cluster.name](http://cluster.name): thisEsCluster [node.name](http://node.name): ${HOSTNAME} cloud.aws.region: eu-west discovery. **ec2**.type: ec2 discovery. **ec2**.groups: elasticsearchCluster discovery. **ec2**.ping\_timeout: 60s cloud.node.auto\_attributes: true discovery.zen.minimum\_master\_nodes: 2 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:30pm UTC](https://discuss.elastic.co/t/cloud-aws-plugin-intermittent-problem-es-1-7-aws-plugin-2-7-1/56891/3 "2017-07-05T22:30:47Z")