# AWS Ubuntu 18, ES 6.6.0, java couldn't find discovery-ec2 plugin **URL:** \ **Category:** Elasticsearch\ **Created:** [April 5, 2019, 7:39am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536 "2019-04-05T07:39:40Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![kunj\_choksi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunj_choksi/32/43531_2.png) [@kunj\_choksi](https://discuss.elastic.co/u/kunj_choksi)\ **Post date:** [April 5, 2019, 7:39am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/1 "2019-04-05T07:39:40Z")
Hey, I have successfully installed ES. But JAVA is still not able to find the discovery-ec2 plugin. Am I missing any plugin or any configuration? below is my yml file ``` cloud.aws.access_key: ##### cloud.aws.secret_key: ##### discovery.type: ec2 network.host: _ec2_ cluster.name: es-clus1 node.name: searchit path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch http.port: 9200 ``` and list of installed plugins ``` ubuntu@ip-172-31-19-5:~$ sudo /usr/share/elasticsearch/bin/elasticsearch-plugin list discovery-ec2 ``` Here is my log ``` [2019-04-05T06:22:56,320][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [searchnode] uncaught exception in thread [main] org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [cloud.aws.secret_key] please check that any required plugins are installed, or check the breaking changes documentation for removed settings at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:163) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-6.6.0.jar:6.6.0] at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:116) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93) ~[elasticsearch-6.6.0.jar:6.6.0] Caused by: java.lang.IllegalArgumentException: unknown setting [cloud.aws.secret_key] please check that any required plugins are installed, or check the breaking changes documentation for removed settings at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:482) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:427) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:398) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:369) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.common.settings.SettingsModule.(SettingsModule.java:148) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.node.Node.(Node.java:372) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.node.Node.(Node.java:265) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:212) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:212) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-6.6.0.jar:6.6.0] ... 6 more Suppressed: java.lang.IllegalArgumentException: unknown setting [cloud.aws.access_key] please check that any required plugins are installed, or check the breaking changes documentation for removed settings at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:482) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:427) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:398) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:369) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.common.settings.SettingsModule.(SettingsModule.java:148) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.node.Node.(Node.java:372) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.node.Node.(Node.java:265) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:212) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:212) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-6.6.0.jar:6.6.0] at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:116) ~[elasticsearch-6.6.0.jar:6.6.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-6.6.0.jar:6.6.0] ``` Here is status of elatsicsarch ``` ubuntu@ip-172-31-19-5:~$ sudo systemctl status elasticsearch ● elasticsearch.service - Elasticsearch Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-04-05 06:22:56 UTC; 1h 12min ago Docs: http://www.elastic.co Process: 15072 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE) Main PID: 15072 (code=exited, status=1/FAILURE) Apr 05 06:22:49 ip-172-31-19-5 systemd[1]: Started Elasticsearch. Apr 05 06:22:49 ip-172-31-19-5 elasticsearch[15072]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. Apr 05 06:22:56 ip-172-31-19-5 systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE Apr 05 06:22:56 ip-172-31-19-5 systemd[1]: elasticsearch.service: Failed with result 'exit-code'. ``` ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 5, 2019, 8:15am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/2 "2019-04-05T08:15:05Z")
The error isn't that it can't find a plugin, it's this: > [@kunj\_choksi](#): > > `unknown setting [cloud.aws.secret_key]` This is not a valid setting, although it was in the past. The [client settings](https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository-s3-client.html) are rather different now. ---
**Author:** ![kunj\_choksi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunj_choksi/32/43531_2.png) [@kunj\_choksi](https://discuss.elastic.co/u/kunj_choksi)\ **Post date:** [April 5, 2019, 9:08am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/3 "2019-04-05T09:08:32Z")
Okk. I have commented out it. Thank you for replying.. But if i want use associated IP on browser and in my web application. What configuration are required in yml? as i tried it by appending port in browser, its shows that site is unreachable. And it show output for curl -XGET "[http://127.0.0.1:9200](http://127.0.0.1:9200)". I have server of AWS Ubuntu EC2. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 5, 2019, 9:12am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/4 "2019-04-05T09:12:20Z")
Sorry, I'm not following. It's unlikely that you will access Elasticsearch directly from a browser, but that seems to be what you're asking about? ---
**Author:** ![kunj\_choksi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunj_choksi/32/43531_2.png) [@kunj\_choksi](https://discuss.elastic.co/u/kunj_choksi)\ **Post date:** [April 5, 2019, 9:15am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/5 "2019-04-05T09:15:20Z")
Yes..i am not able to access it from browser. Is there any configuration in yml? i have added `network.host: 0.0.0.0` ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 5, 2019, 9:17am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/6 "2019-04-05T09:17:50Z")
Can you explain why you want to access Elasticsearch from a web browser? That's not really how it's designed to be used. ---
**Author:** ![kunj\_choksi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunj_choksi/32/43531_2.png) [@kunj\_choksi](https://discuss.elastic.co/u/kunj_choksi)\ **Post date:** [April 5, 2019, 9:21am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/7 "2019-04-05T09:21:36Z")
By means of using it from the browser is that, Am I able to POST or GET requests to the elasticsearch server from my web application? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 5, 2019, 9:34am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/8 "2019-04-05T09:34:58Z")
> [@kunj\_choksi](#): > > Am I able to POST or GET requests to the elasticsearch server from my web application? Do you mean from a Javascript application running in the browser? Yes, this is possible. ---
**Author:** ![kunj\_choksi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunj_choksi/32/43531_2.png) [@kunj\_choksi](https://discuss.elastic.co/u/kunj_choksi)\ **Post date:** [April 5, 2019, 9:39am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/9 "2019-04-05T09:39:02Z")
Yes..from javascript application.. I tried to send request using postman tool. But it couldn't get any response. If i tried curl request in server and i am getting response. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 5, 2019, 9:41am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/10 "2019-04-05T09:41:07Z")
It sounds like a network configuration issue, but you haven't shared much information so it's hard to give much more help. Can you give more details? The requests you're trying and the responses or errors you're seeing? More details about network connectivity between your browser and Elasticsearch? Any firewalls or other filtering? ---
**Author:** ![kunj\_choksi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunj_choksi/32/43531_2.png) [@kunj\_choksi](https://discuss.elastic.co/u/kunj_choksi)\ **Post date:** [April 5, 2019, 9:59am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/11 "2019-04-05T09:59:02Z")
Yes. Server IP: #### I am sending the request to ### by postman Here is server response. ![58%20PM](https://us1.discourse-cdn.com/elastic/original/3X/3/5/35dd154de6341cda1f34de2cfd4a6efd960805c3.png) Firewall status of server ``` ubuntu@ip-172-31-19-5:~$ sudo ufw status Status: active To Action From -- ------ ---- 22 ALLOW Anywhere 9200 ALLOW ### 9200 ALLOW 0.0.0.0 22 (v6) ALLOW Anywhere (v6) ``` elasticsearch.yml ``` cluster.name: es-clus1 node.name: searchit path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch http.port: 9200 network.host: 0.0.0.0 ``` here I am expecting output like ``` ubuntu@ip-172-31-19-5:~$ curl -XGET 'http://127.0.0.1:9200' { "name" : "searchit", "cluster_name" : "es-clus1", "cluster_uuid" : "D5gHXnP3Qu266GM5SsDPsA", "version" : { "number" : "6.6.0", "build_flavor" : "default", "build_type" : "deb", "build_hash" : "a9861f4", "build_date" : "2019-01-24T11:27:09.439740Z", "build_snapshot" : false, "lucene_version" : "7.6.0", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You Know, for Search" } ``` ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 5, 2019, 10:15am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/12 "2019-04-05T10:15:26Z")
Thanks @kunj_choksi. ```auto 9200 ALLOW 0.0.0.0 ``` Does this really mean "allow from anywhere"? I also see `Anywhere` in the `From` column of your firewall config, so I wonder how that differs from `0.0.0.0`. It looks like port 22 is open, which might be SSH? Are you able to SSH from your local machine to this address? ---
**Author:** ![kunj\_choksi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunj_choksi/32/43531_2.png) [@kunj\_choksi](https://discuss.elastic.co/u/kunj_choksi)\ **Post date:** [April 5, 2019, 10:21am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/13 "2019-04-05T10:21:06Z")
`Anywhere` I am not 100% sure means from anywhere but i got a reference from digital ocean tutorial > **[How To Install and Configure Elasticsearch on Ubuntu 16.04 | DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-elasticsearch-on-ubuntu-16-04)** > > Elasticsearch is a platform for distributed search and analysis of data in real time. Its popularity is due to its ease of use, powerful features, and scalability. Elasticsearch is a free and open source software with a solid company behind it:... And yes I am able to SSH to server from my local machine. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 5, 2019, 10:35am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/14 "2019-04-05T10:35:11Z")
Hmm, that page recommends that you _don't_ set up security, which means you'll be exposing an unsecured Elasticsearch cluster to the internet. Please don't do this. There are [many](https://www.teiss.co.uk/threats/elasticsearch-clusters-vulnerable/) bad [stories](https://www.zdnet.com/article/targeted-malware-attacks-against-elasticsearch-clusters-surge/) of [malware](https://www.csoonline.com/article/3345959/elasticsearch-clusters-face-attacks-from-multiple-hacker-groups.html) or [data loss](https://blog.talosintelligence.com/2019/02/cisco-talos-honeypot-analysis-reveals.html) as a result of not properly securing your cluster. The docs you link suggest allowing only a single IP address to contact this cluster (i.e. not `0.0.0.0`), which isn't really satisfactory either, although it's ok for testing. You can find your own IP address by going to [http://icanhazip.com/](http://icanhazip.com/) , and then try using that instead of `0.0.0.0`. But for production use I strongly recommend something more robust. ---
**Author:** ![kunj\_choksi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunj_choksi/32/43531_2.png) [@kunj\_choksi](https://discuss.elastic.co/u/kunj_choksi)\ **Post date:** [April 5, 2019, 11:09am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/15 "2019-04-05T11:09:17Z")
Thank you for concern. I will take care of security. But for testing what should I do for my application? What is blocking my request on the server? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 5, 2019, 11:10am UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/16 "2019-04-05T11:10:10Z")
> [@kunj\_choksi](#): > > What is blocking my request on the server? I think it's the firewall. I think this rule does not allow access from your machine: ```auto 9200 ALLOW 0.0.0.0 ``` Instead you should set up a rule for your specific IP address. ---
**Author:** ![kunj\_choksi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunj_choksi/32/43531_2.png) [@kunj\_choksi](https://discuss.elastic.co/u/kunj_choksi)\ **Post date:** [April 5, 2019, 12:15pm UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/17 "2019-04-05T12:15:14Z")
Thank you so much. I think the problem was with the firewall actually. I have to disable it compulsory. Although I tried to add the rule for my IP. But it didn't allow me to access. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 3, 2019, 12:15pm UTC](https://discuss.elastic.co/t/aws-ubuntu-18-es-6-6-0-java-couldnt-find-discovery-ec2-plugin/175536/18 "2019-05-03T12:15:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.