# AWS ElasticSearch Service MetricBeats

**URL:** https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028
**Category:** Beats
**Tags:** metricbeat
**Created:** [April 7, 2020, 11:52pm UTC](https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028 "2020-04-07T23:52:58Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![vennemp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vennemp/32/66033_2.png) [@vennemp](https://discuss.elastic.co/u/vennemp)
#### Post date: [April 7, 2020, 11:52pm UTC](https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028/1 "2020-04-07T23:52:58Z")

</div>

I am trying to set up MetricBeats with AWS hosted ElasticSearch service. However, in the metricbeats.yml file it asks for a user name and password.. and there isn't a user name and password in AWS ElasticSearch/Kibana for sending data. I have it configured to accept data from every where unauthenticated. Metricbeats is running on my logstash server which is sending data to the same ES cluster with no issues. This is my error message. Please advise.

Couldn't connect to any of the configured Elasticsearch hosts. Errors: [Error connection to Elasticsearch [https://vpc-chzd52f2bk2ay7y5p2fu.us-east-1.es.amazonaws.com:443](https://vpc-chzd52f2bk2ay7y5p2fu.us-east-1.es.amazonaws.com:443): Connection marked as failed because the onConnect callback failed: cannot retrieve the elasticsearch license: unauthorized access, could not connect to the xpack endpoint, verify your credentials]

---

<div class="post-metadata">

### Author: ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)
#### Post date: [April 9, 2020, 5:16pm UTC](https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028/2 "2020-04-09T17:16:08Z")

</div>

Hey @vennemp,

I think that AWS Elasticsearch only includes the Apache licensed features (you can read more about this [here](https://www.elastic.co/aws-elasticsearch-service)). Default Metricbeat packages need some "x-pack" endpoints that are only available in the default Elasticsearch distribution (with Elastic License).  
This error maybe related to the lack of this xpack endpoints and not to authentication issues. You may need to use the OSS distribution of Metricbeat, available here: [https://www.elastic.co/downloads/beats/metricbeat-oss](https://www.elastic.co/downloads/beats/metricbeat-oss)

---

<div class="post-metadata">

### Author: ![vennemp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vennemp/32/66033_2.png) [@vennemp](https://discuss.elastic.co/u/vennemp)
#### Post date: [April 9, 2020, 5:31pm UTC](https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028/3 "2020-04-09T17:31:25Z")

</div>

That makes sense. I knew the AWS flavor of ES/Kibana had some lovely fine print. Unfortunately, I read the Metricbeat OSS version did not support the AWS metrics plug in. If you can confirm that is not the case I would love to implement this.

---

<div class="post-metadata">

### Author: ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)
#### Post date: [April 10, 2020, 10:03am UTC](https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028/4 "2020-04-10T10:03:14Z")

</div>

Yeah, metricbeat OSS doesn't support most of the cloud monitoring features.

---

<div class="post-metadata">

### Author: ![vennemp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vennemp/32/66033_2.png) [@vennemp](https://discuss.elastic.co/u/vennemp)
#### Post date: [April 14, 2020, 3:52pm UTC](https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028/5 "2020-04-14T15:52:52Z")

</div>

Thanks Jaime.. What I don't understand is since Metricbeat AWS Plugin isn't supported in the AWS-flavor of ES, how did I ever get the pre-configured dashboards?? The command metricbeat setup always failed saying I need a user name pw or the x-pack. But clearly the dashboards appeared at some point.. Is there another way they could have appeared?

---

<div class="post-metadata">

### Author: ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)
#### Post date: [April 14, 2020, 4:40pm UTC](https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028/6 "2020-04-14T16:40:11Z")

</div>

Not sure, maybe `metricebeat setup --dashboards` worked at some point?  
In any case I am not sure if data ingestion will work... only Apache Licensed Metricbeat should be used with Apache Licensed Elasticsearch.

---

<div class="post-metadata">

### Author: ![vennemp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vennemp/32/66033_2.png) [@vennemp](https://discuss.elastic.co/u/vennemp)
#### Post date: [April 14, 2020, 4:44pm UTC](https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028/7 "2020-04-14T16:44:53Z")

</div>

The data ingestion didn't work out of the box, but i sent it to logstash and used logstash to send to ES. So that works

 ![Capture](https://us1.discourse-cdn.com/elastic/original/3X/6/6/662536bfa64315a3730b0596be04865061fb714d.png)

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 12, 2020, 4:44pm UTC](https://discuss.elastic.co/t/aws-elasticsearch-service-metricbeats/227028/8 "2020-05-12T16:44:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
