# AWS discovery from filebeat/metricbeat?

**URL:** <https://discuss.elastic.co/t/aws-discovery-from-filebeat-metricbeat/166130>\
**Category:** Beats\
**Created:** [January 29, 2019, 9:56am UTC](https://discuss.elastic.co/t/aws-discovery-from-filebeat-metricbeat/166130 "2019-01-29T09:56:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeremy\_Lecour](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeremy_lecour/32/1416_2.png) [@Jeremy\_Lecour](https://discuss.elastic.co/u/Jeremy_Lecour)\
**Post date:** [January 29, 2019, 9:56am UTC](https://discuss.elastic.co/t/aws-discovery-from-filebeat-metricbeat/166130/1 "2019-01-29T09:56:21Z")

</div>

Hi, my Squid proxy is catching these requests and I wonder if they are from Filebeat or Metricbeat.  
They are the only Go binaries on the server.  
If so, how can I disable this AWS discovery feature ?

```
X.X.X.X - - [07/Jan/2019:18:29:52 +0100] "GET http://169.254.169.254/2009-04-04/meta-data/placement/availability-zone HTTP/1.1" 403 4123 "-" "Go-http-client/1.1" TCP_DENIED:HIER_NONE
X.X.X.X - - [07/Jan/2019:18:29:52 +0100] "GET http://169.254.169.254/metadata/instance/compute? HTTP/1.1" 403 4105 "-" "Go-http-client/1.1" TCP_DENIED:HIER_NONE
X.X.X.X - - [07/Jan/2019:18:29:52 +0100] "GET http://100.100.100.200/latest/meta-data/zone-id HTTP/1.1" 403 4049 "-" "Go-http-client/1.1" TCP_DENIED:HIER_NONE
X.X.X.X - - [07/Jan/2019:18:29:49 +0100] "GET http://169.254.169.254/computeMetadata/v1/? HTTP/1.1" 403 4100 "-" "Go-http-client/1.1" TCP_DENIED:HIER_NONE
X.X.X.X - - [07/Jan/2019:18:29:49 +0100] "GET http://100.100.100.200/latest/meta-data/instance-id HTTP/1.1" 403 4060 "-" "Go-http-client/1.1" TCP_DENIED:HIER_NONE
X.X.X.X - - [07/Jan/2019:18:29:49 +0100] "GET http://169.254.169.254/metadata/v1.json HTTP/1.1" 403 4022 "-" "Go-http-client/1.1" TCP_DENIED:HIER_NONE
```

---

<div class="post-metadata">

**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\
**Post date:** [January 29, 2019, 11:11am UTC](https://discuss.elastic.co/t/aws-discovery-from-filebeat-metricbeat/166130/2 "2019-01-29T11:11:33Z")

</div>

This requests are made by the processor named `add_cloud_metadata`. If you remove this from your list of `processors` in the configuration, you can get rid of these calls.  
See more about this feature: [https://www.elastic.co/guide/en/beats/filebeat/current/add-cloud-metadata.html](https://www.elastic.co/guide/en/beats/filebeat/current/add-cloud-metadata.html)

EDIT: Both Metricbeat and Filebeat has this processor enabled by default.

---

<div class="post-metadata">

**Author:** ![Jeremy\_Lecour](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeremy_lecour/32/1416_2.png) [@Jeremy\_Lecour](https://discuss.elastic.co/u/Jeremy_Lecour)\
**Post date:** [January 29, 2019, 5:20pm UTC](https://discuss.elastic.co/t/aws-discovery-from-filebeat-metricbeat/166130/3 "2019-01-29T17:20:18Z")

</div>

Thank you very much !

---

<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:** [February 26, 2019, 7:20pm UTC](https://discuss.elastic.co/t/aws-discovery-from-filebeat-metricbeat/166130/4 "2019-02-26T19:20:29Z")

</div>

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