https://functions.xpander.ai/aws-eks, which fronts the Amazon EKS API, and carry a signature from the AWS Operator’s IAM role in your cluster, so there is no key to paste.
What the skill can do
API connector: 13 actions, as they appear in the skill panel. 13 of them create, change or delete something in Amazon EKS; mark those under These actions need approval when you add the skill to an agent.- Workload observability (5): Describe Ekscluster, List Eksclusters, List Ekspods, Search Ekslogs, Search Ekspod Logs
- Issue diagnosis (3): Correlate Eksresources, Diagnose Eksissue, Get Eksresource Events
- Insight reporting (2): Get Ekscluster Insights, List Eksinsights
- Log analytics (1): Get Ekspod Logs
- Node observability (1): List Eksnodes
- Service observability (1): List Eksservices
Connect Amazon EKS
In Xpander Chat, open the agent’s settings, click Add skill, and search for Amazon EKS. The connect dialog asks for a connection name and whether the connection is for the Organization (one shared account) or Personal (your own account, so the agent acts with your permissions where systems allow). On an agent other people use, a personal connection runs their requests as you unless the binding requires each person’s own sign-in; see whose credential a shared agent uses. Amazon EKS is served by the AWS Operator in your cluster and signs its calls with the pods’ own AWS identity; there is no key to paste. The IAM setup is on AWS Operator. Calls go tohttps://functions.xpander.ai/aws-eks.

