# Anyone tried installing beats with managed AWS ES? **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [March 1, 2016, 6:07pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146 "2016-03-01T18:07:16Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\ **Post date:** [March 1, 2016, 6:07pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/1 "2016-03-01T18:07:16Z")
Filebeat & Topbeat are getting connection error while trying to connect AWS ES. The logs says, it's adding port (9200) to the host address whereas managed ES endpoint doesn't have a port. ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [March 1, 2016, 6:20pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/2 "2016-03-01T18:20:09Z")
If the port isn't specified then Beats default to 9200. So if you wanted to use port 80 then set `hosts: ['myhost:80']`. ---
**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\ **Post date:** [March 1, 2016, 6:20pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/3 "2016-03-01T18:20:53Z")
But i don't want to use port at all. will it allow that? ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [March 1, 2016, 6:34pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/4 "2016-03-01T18:34:35Z")
If you don't specify a port, then 9200 will be used. [https://www.elastic.co/guide/en/beats/topbeat/current/elasticsearch-output.html#hosts-option](https://www.elastic.co/guide/en/beats/topbeat/current/elasticsearch-output.html#hosts-option) ---
**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\ **Post date:** [March 1, 2016, 6:43pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/5 "2016-03-01T18:43:19Z")
Ok, thanks for confirming. We might need that feature in upcoming release. 🙂 Now I am trying beat-\>logstash-\>ES Thanks & Regards ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [March 2, 2016, 12:12am UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/6 "2016-03-02T00:12:37Z")
Which feature? What's wrong with port 80? Even managed ES must open a port (HTTP default port is 80 btw.), otherwise you won't be able to send or query data. The default port 9200 can be overwritten by the ['port' option](https://www.elastic.co/guide/en/beats/filebeat/current/elasticsearch-output.html#_port_deprecated) (still works) or in the URL given to hosts list. In general default port of elasticsearch is 9200 and default config points to standard default port of elasticsearch. If managesd AWS ES deviates from any defaults, you have to adjust beats configs yourself (never used manages AWS ES myself). ---
**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\ **Post date:** [March 2, 2016, 1:11am UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/7 "2016-03-02T01:11:53Z")
I agree about default ports but managed ES gives only an endpoint in the form of URL, without port. It manages ports internally... The feature I said was to allow host as plain string in case port is not given. I am also creating my own cluster now, not working on managed ES. ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [March 2, 2016, 9:56am UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/8 "2016-03-02T09:56:14Z")
check out [elastic cloud](https://www.elastic.co/cloud). It's managed ES instance hosted on Amazon EC2. Works great for me. ---
**Author:** ![iGaskin](https://avatars.discourse-cdn.com/v4/letter/i/ad7895/32.png) [@iGaskin](https://discuss.elastic.co/u/iGaskin)\ **Post date:** [July 7, 2016, 4:47pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/9 "2016-07-07T16:47:25Z")
I've had success using beats-\>logstash-\>ES. If you were thinking of revisiting Amazon's ES service, you can specify your endpoint (no ports), in the "hosts" field with the logstash-output-amazon\_es plugin [https://github.com/awslabs/logstash-output-amazon\_es](https://github.com/awslabs/logstash-output-amazon_es) ---
**Author:** ![MZL\_Mike](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@MZL\_Mike](https://discuss.elastic.co/u/MZL_Mike)\ **Post date:** [August 24, 2016, 1:28pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/10 "2016-08-24T13:28:40Z")
I'd like to get the beats-\>logstash-\>ES combo to work, but am stuck on the logstash-output-amazon\_es plugin. Specifically, it gets this error when executing the build command: ubuntu@ip-xxx-xxx-xxx-xxx:~$ cd logstash-output-amazon\_es/ ubuntu@ip-xxx-xxx-xxx-xxx:~/logstash-output-amazon\_es$ gem build logstash-output-amazon\_es.gemspec Invalid gemspec in [logstash-output-amazon\_es.gemspec]: undefined method `metadata=' for #\ ERROR: Error loading gemspec. Aborting. Any tips? Which version(s) of logstash and amazon ES and logstash-output-amazon\_es plugin worked for you? ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [August 24, 2016, 2:33pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/11 "2016-08-24T14:33:15Z")
maybe someone in logstash forum can help you. As this plugin is maintained by amazon, I don't really have any experience with it. ---
**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, 9:50pm UTC](https://discuss.elastic.co/t/anyone-tried-installing-beats-with-managed-aws-es/43146/12 "2017-07-05T21:50:43Z")