# Possible to disable auto discovery?
**URL:** https://forums.k8slens.dev/t/possible-to-disable-auto-discovery/3013
**Category:** Lens 2024 Early Access
**Created:** [March 14, 2024, 11:19am UTC](https://forums.k8slens.dev/t/possible-to-disable-auto-discovery/3013 "2024-03-14T11:19:00Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@rob.knight](https://forums.k8slens.dev/u/rob.knight)
#### Post date: [March 14, 2024, 11:19am UTC](https://forums.k8slens.dev/t/possible-to-disable-auto-discovery/3013/1 "2024-03-14T11:19:00Z")
Hi there.
I’m wondering if it’s possible to disable the EKS autodiscovery part of the new lens beta?
For a large org like ours where we have hundreds of AWS profiles setup with many different roles for each account it’s leading to the discovery of thousands of clusters and causing the entire lens UX to grind to a halt as it goes through its discovery process.
The rest of the UI changes look great, but the ability to disable auto discovery I think is a must for anyone with more than a handful of AWS profiles/accounts and I couldn’t see a way to do this in the settings bar.
---
### Author:  [@jakolehm](https://forums.k8slens.dev/u/jakolehm)
#### Post date: [March 14, 2024, 12:15pm UTC](https://forums.k8slens.dev/t/possible-to-disable-auto-discovery/3013/2 "2024-03-14T12:15:50Z")
Thanks for the feedback! We will definitely consider adding an option to disable this functionality.
That said I’m curious to hear does it cause problems if “AWS EKS” node is not expanded in the new Navigator UI? Or only after a user starts to investigate what is inside?
---
### Author:  [@rob.knight](https://forums.k8slens.dev/u/rob.knight)
#### Post date: [March 14, 2024, 12:28pm UTC](https://forums.k8slens.dev/t/possible-to-disable-auto-discovery/3013/3 "2024-03-14T12:28:22Z")
Thanks 🙂 - getting ahead of this to avoid the eventual support case influx is likely wise!
For our users it seems to happen even without opening the EKS drawer. Within a few seconds the whole UI freezes up and we struggle to open even the local kubeconfig autodetected section and despite never touching the EKS discovery tab the entire UI crawls to a halt, memory usage starts increasing and we can see what looks like network attempts to identify the clusters in the background without activating the EKS section.
---
### Author:  [@jakolehm](https://forums.k8slens.dev/u/jakolehm)
#### Post date: [March 14, 2024, 12:30pm UTC](https://forums.k8slens.dev/t/possible-to-disable-auto-discovery/3013/4 "2024-03-14T12:30:54Z")
Ok, that sounds like a bug. The discovery should happen only “on-demand” (meaning when user starts to explore “AWS EKS” section).
---
### Author:  [@jakolehm](https://forums.k8slens.dev/u/jakolehm)
#### Post date: [March 20, 2024, 10:02am UTC](https://forums.k8slens.dev/t/possible-to-disable-auto-discovery/3013/5 "2024-03-20T10:02:23Z")
Next Early Access (beta) update will have few bug fixes related to AWS EKS integration.
---
### Author:  [@jakolehm](https://forums.k8slens.dev/u/jakolehm)
#### Post date: [March 27, 2024, 11:13am UTC](https://forums.k8slens.dev/t/possible-to-disable-auto-discovery/3013/6 "2024-03-27T11:13:27Z")
An update that has AWS EKS fixes is now available. Would be nice if you could give it a run 🙂