# Add\_cloud\_metadata wrong provider

**URL:** <https://discuss.elastic.co/t/add-cloud-metadata-wrong-provider/189780>\
**Category:** Beats\
**Created:** [July 10, 2019, 1:40pm UTC](https://discuss.elastic.co/t/add-cloud-metadata-wrong-provider/189780 "2019-07-10T13:40:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dannyverbeek](https://avatars.discourse-cdn.com/v4/letter/d/67e7ee/32.png) [@dannyverbeek](https://discuss.elastic.co/u/dannyverbeek)\
**Post date:** [July 10, 2019, 1:40pm UTC](https://discuss.elastic.co/t/add-cloud-metadata-wrong-provider/189780/1 "2019-07-10T13:40:39Z")

</div>

I all, we have seen some issues with beats. Both filebeat and metricbeat.

When adding add\_cloud\_metadata is sometimes add openstack as provider, but we run on AWS.  
anyone have this issue?

```auto
add_cloud_metadata.go:351	add_cloud_metadata: hosting provider type detected as openstack, metadata={"availability_zone":"eu-west-1a","instance":{"id":"i-06f92f1c07b994cef","name":"ip-10-84-63-38.eu-west-1.compute.internal"},"machine":{"type":"r5.large"},"provider":"openstack"

```

---

<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:** [August 7, 2019, 3:55pm UTC](https://discuss.elastic.co/t/add-cloud-metadata-wrong-provider/189780/2 "2019-08-07T15:55:08Z")

</div>

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