# Elasticsearch 1.0.1 on AWS **URL:** \ **Category:** Elasticsearch\ **Created:** [March 19, 2014, 3:12pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469 "2014-03-19T15:12:23Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Daniel\_F](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Daniel\_F](https://discuss.elastic.co/u/Daniel_F)\ **Post date:** [March 19, 2014, 3:12pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/1 "2014-03-19T15:12:23Z")
Hi, I am testing Elasticsearch version 1.0.1 on AWS. I have followed documentation of Elasticsearch ([http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/)) and installed latest EC2 plugin. In the log I have seen that the system have recognized the installed plugin but no ec2 discovery logs appeared. For a while I am using unicast discovery but it is really not convenient. Does somebody know if there is a known problem in the plugin? Does the plugin work with 1.0.1 version of Elasticsearch? Any other suggestions are welcome. Thanks, -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 19, 2014, 3:20pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/2 "2014-03-19T15:20:27Z")
cloud-aws 2.0.0.RC1 is supposed to work with es 1.0.1. A new version will come really soon when we will have merged a pending PR. If you want to make sure that everything is running correctly, you could change logging.yml file and set discovery to TRACE -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 19 mars 2014 à 16:12:27, Daniel F. ([feinsteindl@gmail.com](mailto:feinsteindl@gmail.com)) a écrit: Hi, I am testing Elasticsearch version 1.0.1 on AWS. I have followed documentation of Elasticsearch ([http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/)) and installed latest EC2 plugin. In the log I have seen that the system have recognized the installed plugin but no ec2 discovery logs appeared. For a while I am using unicast discovery but it is really not convenient. Does somebody know if there is a known problem in the plugin? Does the plugin work with 1.0.1 version of Elasticsearch? Any other suggestions are welcome. ## Thanks, 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.5329b5bb.8f2b15e.97ca%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.5329b5bb.8f2b15e.97ca%40MacBook-Air-de-David.local). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Daniel\_F](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Daniel\_F](https://discuss.elastic.co/u/Daniel_F)\ **Post date:** [March 19, 2014, 3:51pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/3 "2014-03-19T15:51:08Z")
Thanks David, This is the plugin version I use. In plugins/cloud-aws/ I have elasticsearch-cloud-aws-2.0.0.RC1.jar. The log level is set to TRACE in logging.yml: # discovery discovery: TRACE elasticsearch.yml settings: discovery.zen.ping.multicast.enabled: false cloud: aws: access\_key: XXXX secret\_key: XXXX region: eu-west-1a discovery: type: ec2 groups: my-security-group The log for all discovery records is: [2014-03-19 15:45:12,398][DEBUG][discovery.zen.ping.unicast] [Annie Ghazikhanian] using initial hosts , with concurrent\_connects [10] [2014-03-19 15:45:12,399][DEBUG][discovery.zen] [Annie Ghazikhanian] using ping.timeout [3s], master\_election.filter\_client [true], master\_election.filter\_data [false] [2014-03-19 15:45:12,400][DEBUG][discovery.zen.elect] [Annie Ghazikhanian] using minimum\_master\_nodes [1] [2014-03-19 15:45:12,401][DEBUG][discovery.zen.fd] [Annie Ghazikhanian] [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2014-03-19 15:45:12,420][DEBUG][discovery.zen.fd] [Annie Ghazikhanian] [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2014-03-19 15:45:14,186][TRACE][discovery] [Annie Ghazikhanian] waiting for 30s for the initial state to be set by the discovery [2014-03-19 15:45:17,191][TRACE][discovery.zen] [Annie Ghazikhanian] full ping responses: {none} [2014-03-19 15:45:17,191][DEBUG][discovery.zen] [Annie Ghazikhanian] filtered ping responses: (filter\_client[true], filter\_data[false]) {none} [2014-03-19 15:45:17,223][TRACE][discovery] [Annie Ghazikhanian] initial state set from discovery [2014-03-19 15:45:17,266][INFO][discovery] [Annie Ghazikhanian] toluna-es-test-cluster-eu/1UlTwLC9TsOfg\_Mky1G3Cw As you could see there are no ec2 discovery records in the log. What do I miss? On Wednesday, March 19, 2014 5:20:27 PM UTC+2, David Pilato wrote: > cloud-aws 2.0.0.RC1 is supposed to work with es 1.0.1. > A new version will come really soon when we will have merged a pending PR. > > If you want to make sure that everything is running correctly, you could > change logging.yml file and set discovery to TRACE > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > Le 19 mars 2014 à 16:12:27, Daniel F. ([feins...@gmail.com](mailto:feins...@gmail.com) \) > a écrit: > > Hi, > > I am testing Elasticsearch version 1.0.1 on AWS. I have followed > documentation of Elasticsearch ( > [Elastic — The Search AI Company | Elastic](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/)) and > installed latest EC2 plugin. In the log I have seen that the system have > recognized the installed plugin but no ec2 discovery logs appeared. For a > while I am using unicast discovery but it is really not convenient. > > Does somebody know if there is a known problem in the plugin? Does the > plugin work with 1.0.1 version of Elasticsearch? Any other suggestions are > welcome. > > ## Thanks, > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d28f7292-b0ff-4207-8a35-15fba7a595b8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d28f7292-b0ff-4207-8a35-15fba7a595b8%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Daniel\_F](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Daniel\_F](https://discuss.elastic.co/u/Daniel_F)\ **Post date:** [March 19, 2014, 3:53pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/4 "2014-03-19T15:53:23Z")
Thanks David, This is the plugin version I use. In plugins/cloud-aws/ I have elasticsearch-cloud-aws-2.0.0.RC1.jar. The log level is set to TRACE in logging.yml: # discovery discovery: TRACE elasticsearch.yml settings: discovery.zen.ping.multicast.enabled: false cloud: aws: access\_key: XXXX secret\_key: XXXX region: eu-west-1a discovery: type: ec2 groups: my-security-group The log for all discovery records is: [2014-03-19 15:45:12,398][DEBUG][discovery.zen.ping.unicast] [Annie Ghazikhanian] using initial hosts , with concurrent\_connects [10] [2014-03-19 15:45:12,399][DEBUG][discovery.zen] [Annie Ghazikhanian] using ping.timeout [3s], master\_election.filter\_client [true], master\_election.filter\_data [false] [2014-03-19 15:45:12,400][DEBUG][discovery.zen.elect] [Annie Ghazikhanian] using minimum\_master\_nodes [1] [2014-03-19 15:45:12,401][DEBUG][discovery.zen.fd] [Annie Ghazikhanian] [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2014-03-19 15:45:12,420][DEBUG][discovery.zen.fd] [Annie Ghazikhanian] [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2014-03-19 15:45:14,186][TRACE][discovery] [Annie Ghazikhanian] waiting for 30s for the initial state to be set by the discovery [2014-03-19 15:45:17,191][TRACE][discovery.zen] [Annie Ghazikhanian] full ping responses: {none} [2014-03-19 15:45:17,191][DEBUG][discovery.zen] [Annie Ghazikhanian] filtered ping responses: (filter\_client[true], filter\_data[false]) {none} [2014-03-19 15:45:17,223][TRACE][discovery] [Annie Ghazikhanian] initial state set from discovery [2014-03-19 15:45:17,266][INFO][discovery] [Annie Ghazikhanian] toluna-es-test-cluster-eu/1UlTwLC9TsOfg\_Mky1G3Cw As you could see there are no ec2 discovery records in the log. What do I miss? On Wednesday, March 19, 2014 5:12:23 PM UTC+2, Daniel F. wrote: > Hi, > > I am testing Elasticsearch version 1.0.1 on AWS. I have followed > documentation of Elasticsearch ( > [Elastic — The Search AI Company | Elastic](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/)) and > installed latest EC2 plugin. In the log I have seen that the system have > recognized the installed plugin but no ec2 discovery logs appeared. For a > while I am using unicast discovery but it is really not convenient. > > Does somebody know if there is a known problem in the plugin? Does the > plugin work with 1.0.1 version of Elasticsearch? Any other suggestions are > welcome. > > Thanks, -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/bb6aee32-d324-4d55-81cb-9afde783a3c0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/bb6aee32-d324-4d55-81cb-9afde783a3c0%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 19, 2014, 4:07pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/5 "2014-03-19T16:07:34Z")
In elasticsearch-cloud-aws-2.0.0.RC1.zip file you should find other files. Your did not download the ZIP file I guess. May be you add a line break between discovery.zen.ping.multicast.enabled: false and cloud: -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 19 mars 2014 à 16:53:26, Daniel F. ([feinsteindl@gmail.com](mailto:feinsteindl@gmail.com)) a écrit: Thanks David, This is the plugin version I use. In plugins/cloud-aws/ I have elasticsearch-cloud-aws-2.0.0.RC1.jar. The log level is set to TRACE in logging.yml: # discovery discovery: TRACE elasticsearch.yml settings: discovery.zen.ping.multicast.enabled: false cloud: aws: access\_key: XXXX secret\_key: XXXX region: eu-west-1a discovery: type: ec2 groups: my-security-group The log for all discovery records is: [2014-03-19 15:45:12,398][DEBUG][discovery.zen.ping.unicast] [Annie Ghazikhanian] using initial hosts [], with concurrent\_connects [10] [2014-03-19 15:45:12,399][DEBUG][discovery.zen] [Annie Ghazikhanian] using ping.timeout [3s], master\_election.filter\_client [true], master\_election.filter\_data [false] [2014-03-19 15:45:12,400][DEBUG][discovery.zen.elect] [Annie Ghazikhanian] using minimum\_master\_nodes [1] [2014-03-19 15:45:12,401][DEBUG][discovery.zen.fd] [Annie Ghazikhanian] [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2014-03-19 15:45:12,420][DEBUG][discovery.zen.fd] [Annie Ghazikhanian] [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2014-03-19 15:45:14,186][TRACE][discovery] [Annie Ghazikhanian] waiting for 30s for the initial state to be set by the discovery [2014-03-19 15:45:17,191][TRACE][discovery.zen] [Annie Ghazikhanian] full ping responses: {none} [2014-03-19 15:45:17,191][DEBUG][discovery.zen] [Annie Ghazikhanian] filtered ping responses: (filter\_client[true], filter\_data[false]) {none} [2014-03-19 15:45:17,223][TRACE][discovery] [Annie Ghazikhanian] initial state set from discovery [2014-03-19 15:45:17,266][INFO][discovery] [Annie Ghazikhanian] toluna-es-test-cluster-eu/1UlTwLC9TsOfg\_Mky1G3Cw As you could see there are no ec2 discovery records in the log. What do I miss? On Wednesday, March 19, 2014 5:12:23 PM UTC+2, Daniel F. wrote: Hi, I am testing Elasticsearch version 1.0.1 on AWS. I have followed documentation of Elasticsearch ([http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/)) and installed latest EC2 plugin. In the log I have seen that the system have recognized the installed plugin but no ec2 discovery logs appeared. For a while I am using unicast discovery but it is really not convenient. Does somebody know if there is a known problem in the plugin? Does the plugin work with 1.0.1 version of Elasticsearch? Any other suggestions are welcome. ## Thanks, 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/bb6aee32-d324-4d55-81cb-9afde783a3c0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/bb6aee32-d324-4d55-81cb-9afde783a3c0%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.5329c0c6.76272110.97ca%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.5329c0c6.76272110.97ca%40MacBook-Air-de-David.local). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Daniel\_F](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Daniel\_F](https://discuss.elastic.co/u/Daniel_F)\ **Post date:** [March 19, 2014, 4:24pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/6 "2014-03-19T16:24:25Z")
Sorry for confusion I have tried to post only relevant information here. There are many lines between discovery.zen.ping.multicast.enabled: false and ec2 discovery configurations. In the folder plugins/cloud-aws/ I have the following files: -rw-r--r-- 1 root root 9276981 Mar 9 11:53 aws-java-sdk-1.3.32.jar -rw-r--r-- 1 root root 58160 Mar 9 11:53 commons-codec-1.4.jar -rw-r--r-- 1 root root 60686 Mar 9 11:53 commons-logging-1.1.1.jar -rw-r--r-- 1 root root 45197 Mar 9 11:53 elasticsearch-cloud-aws-2.0.0.RC1.jar -rw-r--r-- 1 root root 351132 Mar 9 11:53 httpclient-4.1.1.jar -rw-r--r-- 1 root root 181041 Mar 9 11:53 httpcore-4.1.jar On Wednesday, March 19, 2014 5:12:23 PM UTC+2, Daniel F. wrote: > Hi, > > I am testing Elasticsearch version 1.0.1 on AWS. I have followed > documentation of Elasticsearch ( > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/)) and > installed latest EC2 plugin. In the log I have seen that the system have > recognized the installed plugin but no ec2 discovery logs appeared. For a > while I am using unicast discovery but it is really not convenient. > > Does somebody know if there is a known problem in the plugin? Does the > plugin work with 1.0.1 version of Elasticsearch? Any other suggestions are > welcome. > > Thanks, -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/fde9d055-a854-412c-8f76-5c7bafc07cd9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fde9d055-a854-412c-8f76-5c7bafc07cd9%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 19, 2014, 4:25pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/7 "2014-03-19T16:25:59Z")
Are you running elasticsearch as root? May be you should chown -R elasticsearch /plugins -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 19 mars 2014 à 17:24:29, Daniel F. ([feinsteindl@gmail.com](mailto:feinsteindl@gmail.com)) a écrit: Sorry for confusion I have tried to post only relevant information here. There are many lines between discovery.zen.ping.multicast.enabled: false and ec2 discovery configurations. In the folder plugins/cloud-aws/ I have the following files: -rw-r--r-- 1 root root 9276981 Mar 9 11:53 aws-java-sdk-1.3.32.jar -rw-r--r-- 1 root root 58160 Mar 9 11:53 commons-codec-1.4.jar -rw-r--r-- 1 root root 60686 Mar 9 11:53 commons-logging-1.1.1.jar -rw-r--r-- 1 root root 45197 Mar 9 11:53 elasticsearch-cloud-aws-2.0.0.RC1.jar -rw-r--r-- 1 root root 351132 Mar 9 11:53 httpclient-4.1.1.jar -rw-r--r-- 1 root root 181041 Mar 9 11:53 httpcore-4.1.jar On Wednesday, March 19, 2014 5:12:23 PM UTC+2, Daniel F. wrote: Hi, I am testing Elasticsearch version 1.0.1 on AWS. I have followed documentation of Elasticsearch ([http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/)) and installed latest EC2 plugin. In the log I have seen that the system have recognized the installed plugin but no ec2 discovery logs appeared. For a while I am using unicast discovery but it is really not convenient. Does somebody know if there is a known problem in the plugin? Does the plugin work with 1.0.1 version of Elasticsearch? Any other suggestions are welcome. ## Thanks, 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/fde9d055-a854-412c-8f76-5c7bafc07cd9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fde9d055-a854-412c-8f76-5c7bafc07cd9%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.5329c517.46b7d447.97ca%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.5329c517.46b7d447.97ca%40MacBook-Air-de-David.local). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Daniel\_F](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Daniel\_F](https://discuss.elastic.co/u/Daniel_F)\ **Post date:** [March 19, 2014, 6:30pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/8 "2014-03-19T18:30:57Z")
Yes, i am running elasticsearch as root. It is a test environment so I did not tune it yet. -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 19, 2014, 8:21pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/9 "2014-03-19T20:21:36Z")
I think your elasticsearch.yml is incorrect. Just saying because as far as I can see, ec2 discovery does not start actually. So, may be some space before cloud.type: ec2 is missing? -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 19 mars 2014 à 19:31:03, Daniel F. ([feinsteindl@gmail.com](mailto:feinsteindl@gmail.com)) a écrit: ## Yes, i am running elasticsearch as root. It is a test environment so I did not tune it yet. 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.5329fc50.5f3534a4.97ca%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.5329fc50.5f3534a4.97ca%40MacBook-Air-de-David.local). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Daniel\_F](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Daniel\_F](https://discuss.elastic.co/u/Daniel_F)\ **Post date:** [March 19, 2014, 10:21pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/10 "2014-03-19T22:21:36Z")
Thanks David, You are right elasticsearch.yml had two errors: space before "discovery" and "region" should not be equal to availability zone "eu-west-1a" but " eu-west-1". The working version is: discovery.zen.ping.multicast.enabled: false cloud: aws: access\_key: XXXX secret\_key: XXXX region: eu-west-1 discovery: type: ec2 groups: my-security-group Daniel On Wednesday, March 19, 2014 10:21:36 PM UTC+2, David Pilato wrote: > I think your elasticsearch.yml is incorrect. > > Just saying because as far as I can see, ec2 discovery does not start > actually. > So, may be some space before cloud.type: ec2 is missing? > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > Le 19 mars 2014 à 19:31:03, Daniel F. ([feins...@gmail.com](mailto:feins...@gmail.com) \) > a écrit: > > ## Yes, i am running elasticsearch as root. It is a test environment so I did not tune it yet. > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d079915d-b1fb-4ca4-8634-3e35ab460d9a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d079915d-b1fb-4ca4-8634-3e35ab460d9a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Geet\_Gangwar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geet_gangwar/32/1720_2.png) [@Geet\_Gangwar](https://discuss.elastic.co/u/Geet_Gangwar)\ **Post date:** [March 21, 2014, 7:08am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/11 "2014-03-21T07:08:36Z")
Hi I am also facing same issue of no dicovery.ec2 logs getting generated for elasticsearch 1.0.1 and cloud-aws plugin 2.0.0.RC I tried the corrected version of setting given: cloud: aws: access\_key: XXXXXX secret\_key: XXXXXX region: ap-southeast-1 discovery: type: ec2 groups: Difference is the region. I have created two nodes(one is master node with node.data = false and other one is just a data node with node.master = false) Even when I try for unicast and specify hard coded private ip then also the second node does not joins the cluster. I installed head plugin on the master node which is working fine and I m able to view one node in the browser. Please guide me on what I am doing wrong. On Thursday, March 20, 2014 3:51:36 AM UTC+5:30, Daniel F. wrote: > Thanks David, > > You are right elasticsearch.yml had two errors: space before "discovery" > and "region" should not be equal to availability zone "eu-west-1a" but " > eu-west-1". > > The working version is: > > discovery.zen.ping.multicast.enabled: false > > cloud: > aws: > access\_key: XXXX > secret\_key: XXXX > region: eu-west-1 > discovery: > type: ec2 > groups: my-security-group > > Daniel > > On Wednesday, March 19, 2014 10:21:36 PM UTC+2, David Pilato wrote: > > > I think your elasticsearch.yml is incorrect. > > > > Just saying because as far as I can see, ec2 discovery does not start > > actually. > > So, may be some space before cloud.type: ec2 is missing? > > > > -- > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > > > Le 19 mars 2014 à 19:31:03, Daniel F. ([feins...@gmail.com](mailto:feins...@gmail.com)) a écrit: > > > > ## Yes, i am running elasticsearch as root. It is a test environment so I did not tune it yet. > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 21, 2014, 7:13am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/12 "2014-03-21T07:13:31Z")
They are sharing same security group name and are deployed in same region? If unicast does not work using private IP, aws plugin won't work either. Can you from one node run curl [http://secondnodeip:9200/](http://secondnodeip:9200/) Same from second node. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 21 mars 2014 à 08:08, Geet Gangwar [geetgangwar@gmail.com](mailto:geetgangwar@gmail.com) a écrit : Hi I am also facing same issue of no dicovery.ec2 logs getting generated for elasticsearch 1.0.1 and cloud-aws plugin 2.0.0.RC I tried the corrected version of setting given: cloud: aws: access\_key: XXXXXX secret\_key: XXXXXX region: ap-southeast-1 discovery: type: ec2 groups: Difference is the region. I have created two nodes(one is master node with node.data = false and other one is just a data node with node.master = false) Even when I try for unicast and specify hard coded private ip then also the second node does not joins the cluster. I installed head plugin on the master node which is working fine and I m able to view one node in the browser. Please guide me on what I am doing wrong. > On Thursday, March 20, 2014 3:51:36 AM UTC+5:30, Daniel F. wrote: > Thanks David, > > You are right elasticsearch.yml had two errors: space before "discovery" and "region" should not be equal to availability zone "eu-west-1a" but "eu-west-1". > > The working version is: > > discovery.zen.ping.multicast.enabled: false > > cloud: > aws: > access\_key: XXXX > secret\_key: XXXX > region: eu-west-1 > discovery: > type: ec2 > groups: my-security-group > > Daniel > > > On Wednesday, March 19, 2014 10:21:36 PM UTC+2, David Pilato wrote: > > I think your elasticsearch.yml is incorrect. > > > > Just saying because as far as I can see, ec2 discovery does not start actually. > > So, may be some space before cloud.type: ec2 is missing? > > > > -- > > David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) > > @dadoonet | @elasticsearchfr > > > > > Le 19 mars 2014 à 19:31:03, Daniel F. ([feins...@gmail.com](mailto:feins...@gmail.com)) a écrit: > > > > > > ## Yes, i am running elasticsearch as root. It is a test environment so I did not tune it yet. > > > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com). > > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Geet\_Gangwar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geet_gangwar/32/1720_2.png) [@Geet\_Gangwar](https://discuss.elastic.co/u/Geet_Gangwar)\ **Post date:** [March 21, 2014, 8:33am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/13 "2014-03-21T08:33:12Z")
Thanks David for such a quick reply. I tried you command from one node to second node and got following result. { "status" : 503, "name" : "cleandata-DataNode-1", "version" : { "number" : "1.0.1", "build\_hash" : "5c03844e1978e5cc924dab2a423dc63ce881c42b", "build\_timestamp" : "2014-02-25T15:52:53Z", "build\_snapshot" : false, "lucene\_version" : "4.6" }, "tagline" : "You Know, for Search" } Dont know whehter it is correct or something is wrong. Regards Geet On Fri, Mar 21, 2014 at 12:43 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > They are sharing same security group name and are deployed in same region? > If unicast does not work using private IP, aws plugin won't work either. > > Can you from one node run > > curl [http://secondnodeip:9200/](http://secondnodeip:9200/) > > Same from second node. > > -- > David 😉 > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 21 mars 2014 à 08:08, Geet Gangwar [geetgangwar@gmail.com](mailto:geetgangwar@gmail.com) a écrit : > > Hi > > I am also facing same issue of no dicovery.ec2 logs getting generated for > elasticsearch 1.0.1 and cloud-aws plugin 2.0.0.RC > > I tried the corrected version of setting given: > > cloud: > aws: > access\_key: XXXXXX > secret\_key: XXXXXX > region: ap-southeast-1 > discovery: > type: ec2 > groups: > > Difference is the region. > > I have created two nodes(one is master node with node.data = false and > other one is just a data node with node.master = false) > > Even when I try for unicast and specify hard coded private ip then also > the second node does not joins the cluster. > > I installed head plugin on the master node which is working fine and I m > able to view one node in the browser. > > Please guide me on what I am doing wrong. > > On Thursday, March 20, 2014 3:51:36 AM UTC+5:30, Daniel F. wrote: > > > Thanks David, > > > > You are right elasticsearch.yml had two errors: space before "discovery" > > and "region" should not be equal to availability zone "eu-west-1a" but " > > eu-west-1". > > > > The working version is: > > > > discovery.zen.ping.multicast.enabled: false > > > > cloud: > > aws: > > access\_key: XXXX > > secret\_key: XXXX > > region: eu-west-1 > > discovery: > > type: ec2 > > groups: my-security-group > > > > Daniel > > > > On Wednesday, March 19, 2014 10:21:36 PM UTC+2, David Pilato wrote: > > > > > I think your elasticsearch.yml is incorrect. > > > > > > Just saying because as far as I can see, ec2 discovery does not start > > > actually. > > > So, may be some space before cloud.type: ec2 is missing? > > > > > > -- > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > > > > > Le 19 mars 2014 à 19:31:03, Daniel F. ([feins...@gmail.com](mailto:feins...@gmail.com)) a écrit: > > > > > > ## Yes, i am running elasticsearch as root. It is a test environment so I did not tune it yet. > > > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e% > > > [40googlegroups.com](http://40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/VyFXBVFp\_oM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/VyFXBVFp_oM/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr)[https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3\_7xDe-Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3_7xDe-Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 21, 2014, 8:47am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/14 "2014-03-21T08:47:40Z")
status is incorrect but I guess it's due to the fact your data node is not a master node and can't find a master. How did you set unicast? -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 21 mars 2014 à 09:33:35, Geet Gangwar ([geetgangwar@gmail.com](mailto:geetgangwar@gmail.com)) a écrit: Thanks David for such a quick reply. I tried you command from one node to second node and got following result. { "status" : 503, "name" : "cleandata-DataNode-1", "version" : { "number" : "1.0.1", "build\_hash" : "5c03844e1978e5cc924dab2a423dc63ce881c42b", "build\_timestamp" : "2014-02-25T15:52:53Z", "build\_snapshot" : false, "lucene\_version" : "4.6" }, "tagline" : "You Know, for Search" } Dont know whehter it is correct or something is wrong. Regards Geet On Fri, Mar 21, 2014 at 12:43 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: They are sharing same security group name and are deployed in same region? If unicast does not work using private IP, aws plugin won't work either. Can you from one node run curl [http://secondnodeip:9200/](http://secondnodeip:9200/) Same from second node. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 21 mars 2014 à 08:08, Geet Gangwar [geetgangwar@gmail.com](mailto:geetgangwar@gmail.com) a écrit : Hi I am also facing same issue of no dicovery.ec2 logs getting generated for elasticsearch 1.0.1 and cloud-aws plugin 2.0.0.RC I tried the corrected version of setting given: cloud: aws: access\_key: XXXXXX secret\_key: XXXXXX region: ap-southeast-1 discovery: type: ec2 groups: Difference is the region. I have created two nodes(one is master node with node.data = false and other one is just a data node with node.master = false) Even when I try for unicast and specify hard coded private ip then also the second node does not joins the cluster. I installed head plugin on the master node which is working fine and I m able to view one node in the browser. Please guide me on what I am doing wrong. On Thursday, March 20, 2014 3:51:36 AM UTC+5:30, Daniel F. wrote: Thanks David, You are right elasticsearch.yml had two errors: space before "discovery" and "region" should not be equal to availability zone "eu-west-1a" but "eu-west-1". The working version is: discovery.zen.ping.multicast.enabled: false cloud: aws: access\_key: XXXX secret\_key: XXXX region: eu-west-1 discovery: type: ec2 groups: my-security-group Daniel On Wednesday, March 19, 2014 10:21:36 PM UTC+2, David Pilato wrote: I think your elasticsearch.yml is incorrect. Just saying because as far as I can see, ec2 discovery does not start actually. So, may be some space before cloud.type: ec2 is missing? -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 19 mars 2014 à 19:31:03, Daniel F. ([feins...@gmail.com](mailto:feins...@gmail.com)) a écrit: ## Yes, i am running elasticsearch as root. It is a test environment so I did not tune it yet. ## 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). ## To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group. To unsubscribe from this topic, visit [https://groups.google.com/d/topic/elasticsearch/VyFXBVFp\_oM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/VyFXBVFp_oM/unsubscribe). To unsubscribe from this group and all its topics, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr). For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3\_7xDe-Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3_7xDe-Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Geet\_Gangwar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geet_gangwar/32/1720_2.png) [@Geet\_Gangwar](https://discuss.elastic.co/u/Geet_Gangwar)\ **Post date:** [March 21, 2014, 9:16am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/15 "2014-03-21T09:16:28Z")
I have set private ip of my data node. discovery.zen.ping.unicast.hosts: ["10.142.181.16"] and have disabled the multicast discovery.zen.ping.multicast.enabled: false Regards Geet On Fri, Mar 21, 2014 at 2:17 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > status is incorrect but I guess it's due to the fact your data node is not > a master node and can't find a master. > > How did you set unicast? > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > Le 21 mars 2014 à 09:33:35, Geet Gangwar ([geetgangwar@gmail.com](mailto:geetgangwar@gmail.com)) a écrit: > > Thanks David for such a quick reply. > > I tried you command from one node to second node and got following result. > > { > "status" : 503, > "name" : "cleandata-DataNode-1", > "version" : { > "number" : "1.0.1", > "build\_hash" : "5c03844e1978e5cc924dab2a423dc63ce881c42b", > "build\_timestamp" : "2014-02-25T15:52:53Z", > "build\_snapshot" : false, > "lucene\_version" : "4.6" > }, > "tagline" : "You Know, for Search" > } > > Dont know whehter it is correct or something is wrong. > > Regards > > Geet > > On Fri, Mar 21, 2014 at 12:43 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > > > They are sharing same security group name and are deployed in same > > region? > > If unicast does not work using private IP, aws plugin won't work either. > > > > Can you from one node run > > > > curl [http://secondnodeip:9200/](http://secondnodeip:9200/) > > > > Same from second node. > > > > -- > > David 😉 > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > > Le 21 mars 2014 à 08:08, Geet Gangwar [geetgangwar@gmail.com](mailto:geetgangwar@gmail.com) a écrit : > > > > Hi > > > > I am also facing same issue of no dicovery.ec2 logs getting generated for > > elasticsearch 1.0.1 and cloud-aws plugin 2.0.0.RC > > > > I tried the corrected version of setting given: > > > > cloud: > > aws: > > access\_key: XXXXXX > > secret\_key: XXXXXX > > region: ap-southeast-1 > > discovery: > > type: ec2 > > groups: > > > > Difference is the region. > > > > I have created two nodes(one is master node with node.data = false and > > other one is just a data node with node.master = false) > > > > Even when I try for unicast and specify hard coded private ip then also > > the second node does not joins the cluster. > > > > I installed head plugin on the master node which is working fine and I m > > able to view one node in the browser. > > > > Please guide me on what I am doing wrong. > > > > On Thursday, March 20, 2014 3:51:36 AM UTC+5:30, Daniel F. wrote: > > > > > Thanks David, > > > > > > You are right elasticsearch.yml had two errors: space before "discovery" > > > and "region" should not be equal to availability zone "eu-west-1a" but " > > > eu-west-1". > > > > > > The working version is: > > > > > > discovery.zen.ping.multicast.enabled: false > > > > > > cloud: > > > aws: > > > access\_key: XXXX > > > secret\_key: XXXX > > > region: eu-west-1 > > > discovery: > > > type: ec2 > > > groups: my-security-group > > > > > > Daniel > > > > > > On Wednesday, March 19, 2014 10:21:36 PM UTC+2, David Pilato wrote: > > > > > > > I think your elasticsearch.yml is incorrect. > > > > > > > > Just saying because as far as I can see, ec2 discovery does not start > > > > actually. > > > > So, may be some space before cloud.type: ec2 is missing? > > > > > > > > ``` > > > > -- > > > > > > > > ``` > > > > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > > > > > > > Le 19 mars 2014 à 19:31:03, Daniel F. ([feins...@gmail.com](mailto:feins...@gmail.com)) a écrit: > > > > > > > > ## Yes, i am running elasticsearch as root. It is a test environment so I did not tune it yet. > > > > > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit > > > > [https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > ## To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com?utm_medium=email&utm_source=footer) . For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/VyFXBVFp\_oM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/VyFXBVFp_oM/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr)[https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr?utm_medium=email&utm_source=footer). > > > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3\_7xDe-Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3_7xDe-Q%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3\_7xDe-Q%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3_7xDe-Q%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/VyFXBVFp\_oM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/VyFXBVFp_oM/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local)[https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEXePwcVNDYoNQ%3DdA8eTtiq5J6aXLZZtioRN-DE-o8YOR2OBNg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEXePwcVNDYoNQ%3DdA8eTtiq5J6aXLZZtioRN-DE-o8YOR2OBNg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Geet\_Gangwar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geet_gangwar/32/1720_2.png) [@Geet\_Gangwar](https://discuss.elastic.co/u/Geet_Gangwar)\ **Post date:** [March 21, 2014, 10:07am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/16 "2014-03-21T10:07:46Z")
Hi David, I tried unicast with making my removing the node.master=false. Now any of my node can become master. I this case unicast is working but I have to manually do the unicat setting in both nodes. I have also installed cloud-aws plugin on both nodes, still no logs are getting generated for ec2 discovery. Regards Geet On Fri, Mar 21, 2014 at 2:46 PM, Geet Gangwar [geetgangwar@gmail.com](mailto:geetgangwar@gmail.com) wrote: > I have set private ip of my data node. > > discovery.zen.ping.unicast.hosts: ["10.142.181.16"] > and have disabled the multicast > > discovery.zen.ping.multicast.enabled: false > > Regards > > Geet > > On Fri, Mar 21, 2014 at 2:17 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > > > status is incorrect but I guess it's due to the fact your data node is > > not a master node and can't find a master. > > > > How did you set unicast? > > > > -- > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > > > Le 21 mars 2014 à 09:33:35, Geet Gangwar ([geetgangwar@gmail.com](mailto:geetgangwar@gmail.com)) a écrit: > > > > Thanks David for such a quick reply. > > > > I tried you command from one node to second node and got following result. > > > > { > > "status" : 503, > > "name" : "cleandata-DataNode-1", > > "version" : { > > "number" : "1.0.1", > > "build\_hash" : "5c03844e1978e5cc924dab2a423dc63ce881c42b", > > "build\_timestamp" : "2014-02-25T15:52:53Z", > > "build\_snapshot" : false, > > "lucene\_version" : "4.6" > > }, > > "tagline" : "You Know, for Search" > > } > > > > Dont know whehter it is correct or something is wrong. > > > > Regards > > > > Geet > > > > On Fri, Mar 21, 2014 at 12:43 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > > > > > They are sharing same security group name and are deployed in same > > > region? > > > If unicast does not work using private IP, aws plugin won't work either. > > > > > > Can you from one node run > > > > > > curl [http://secondnodeip:9200/](http://secondnodeip:9200/) > > > > > > Same from second node. > > > > > > -- > > > David 😉 > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > > > > Le 21 mars 2014 à 08:08, Geet Gangwar [geetgangwar@gmail.com](mailto:geetgangwar@gmail.com) a écrit : > > > > > > Hi > > > > > > I am also facing same issue of no dicovery.ec2 logs getting generated > > > for elasticsearch 1.0.1 and cloud-aws plugin 2.0.0.RC > > > > > > I tried the corrected version of setting given: > > > > > > cloud: > > > aws: > > > access\_key: XXXXXX > > > secret\_key: XXXXXX > > > region: ap-southeast-1 > > > discovery: > > > type: ec2 > > > groups: > > > > > > Difference is the region. > > > > > > I have created two nodes(one is master node with node.data = false and > > > other one is just a data node with node.master = false) > > > > > > Even when I try for unicast and specify hard coded private ip then also > > > the second node does not joins the cluster. > > > > > > I installed head plugin on the master node which is working fine and I m > > > able to view one node in the browser. > > > > > > Please guide me on what I am doing wrong. > > > > > > On Thursday, March 20, 2014 3:51:36 AM UTC+5:30, Daniel F. wrote: > > > > > > > Thanks David, > > > > > > > > You are right elasticsearch.yml had two errors: space before > > > > "discovery" and "region" should not be equal to availability zone " > > > > eu-west-1a" but "eu-west-1". > > > > > > > > The working version is: > > > > > > > > discovery.zen.ping.multicast.enabled: false > > > > > > > > cloud: > > > > aws: > > > > access\_key: XXXX > > > > secret\_key: XXXX > > > > region: eu-west-1 > > > > discovery: > > > > type: ec2 > > > > groups: my-security-group > > > > > > > > Daniel > > > > > > > > On Wednesday, March 19, 2014 10:21:36 PM UTC+2, David Pilato wrote: > > > > > > > > > I think your elasticsearch.yml is incorrect. > > > > > > > > > > Just saying because as far as I can see, ec2 discovery does not start > > > > > actually. > > > > > So, may be some space before cloud.type: ec2 is missing? > > > > > > > > > > ``` > > > > > -- > > > > > > > > > > ``` > > > > > > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > > > > > > > > > Le 19 mars 2014 à 19:31:03, Daniel F. ([feins...@gmail.com](mailto:feins...@gmail.com)) a écrit: > > > > > > > > > > ## Yes, i am running elasticsearch as root. It is a test environment so I did not tune it yet. > > > > > > > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit > > > > > [https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > > > ## To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com?utm_medium=email&utm_source=footer) . For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/VyFXBVFp\_oM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/VyFXBVFp_oM/unsubscribe). > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr)[https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr?utm_medium=email&utm_source=footer). > > > > > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3\_7xDe-Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3_7xDe-Q%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3\_7xDe-Q%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3_7xDe-Q%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/VyFXBVFp\_oM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/VyFXBVFp_oM/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local)[https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEXePweAsnd5e5WJZfw0ERR8YRLAYeApgFfSzLABhjccq6VDkw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEXePweAsnd5e5WJZfw0ERR8YRLAYeApgFfSzLABhjccq6VDkw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:41am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-1-on-aws/16469/17 "2017-07-06T01:41:36Z")