# Can't disable Kibana calls to 169.254.169.254

**URL:** <https://discuss.elastic.co/t/cant-disable-kibana-calls-to-169-254-169-254/385018>\
**Category:** Kibana\
**Created:** [February 12, 2026, 10:01am UTC](https://discuss.elastic.co/t/cant-disable-kibana-calls-to-169-254-169-254/385018 "2026-02-12T10:01:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fentom](https://avatars.discourse-cdn.com/v4/letter/f/e5b9ba/32.png) [@fentom](https://discuss.elastic.co/u/fentom)\
**Post date:** [February 12, 2026, 10:01am UTC](https://discuss.elastic.co/t/cant-disable-kibana-calls-to-169-254-169-254/385018/1 "2026-02-12T10:01:40Z")

</div>

I’m running Kibana and Elasticsearch using ECK Operator on an air gapped K8s cluster which also uses Cilium to configure network policies.  
In the Hubble UI provided by Cilium I can see that requests from Elasticsearch and Kibana to 169.254.169.254, which seems to be an instance metadata service from cloud providers, are dropped. To keep my Cilium logs clean I want to disable the features which are responsible to send these requests.

To disable this for Elasticsearch I set the environment variable `AWS_EC2_METADATA_DISABLED` to `true` and the requests stopped.

For Kibana I tried a lot of things but don’t get these request stopping.

I tried following for Kibana:

- Setting environment variable `AWS_EC2_METADATA_DISABLED` to `true`
- Setting Kibana config parameter `telemetry.optIn` to `false`
- Setting Kibana config parameter `xpack.fleet.isAirGapped` to `true`
- Setting Kibana config parameter `newsfeed.enabled` to `false`
- Setting Kibana config parameter `map.includeElasticMapsService` to `false`
- Setting Kibana config parameter `xpack.product_intercept.enabled` to `true`