AWS EKS and Azure AKS integrations
EKS or AKS clusters you cannot see?
Connect the account and autodiscover your clusters.
How Lens resolves it
Every cluster in the account, found for you
Lens queries your cloud accounts for their Kubernetes clusters. You do not name a cluster, a region, or a profile.
Across accounts and subscriptions
Discovery runs across all your AWS accounts and all your Azure subscriptions. One EKS integration returns every cluster the account holds.
Your access role scopes the list
Sign in through IAM Identity Center or Microsoft Entra. When your own permissions stop short of the clusters, assume the IAM role that reaches them.
Synced, not snapshotted
New clusters appear and retired ones drop out. Select Refresh to re-run discovery for an account without waiting.
In the navigator
Grouped the way your cloud groups them
EKS clusters arrive under the AWS profile they came from. AKS clusters arrive under their Azure directory and resource group, with a connection dot on each.
Open a cluster and work
Select a discovered cluster and Lens connects to it. No kubeconfig entry is written to your machine.
Private AKS clusters included
Private clusters are listed next to the public ones. Lens reaches them over the Azure-managed network path.
Rename a resource group
Give an Azure resource group a clearer label in Lens. The rename is local and does not change anything in Azure.
What it replaces
No CLI, no update-kubeconfig, no cluster list to maintain
Free. No payment details needed.
Try cluster discovery in the Lens 14-day trial
Every premium feature, unlocked for 14 days.
Download Lens Desktop and create your Lens ID from the app. Your 14 days start there. When the trial ends, your configuration is kept and the features lock until you upgrade.