AWS SSO and EKS

EKS contexts usually authenticate through the aws CLI (aws eks get-token) with a named profile. KubeDrive runs the same command your kubeconfig names, so anything that works with kubectl works here.

Before you start

  • Install the AWS CLI v2 and sign in once from a terminal: aws sso login --profile <name>.
  • Make sure the profile in your kubeconfig (--profile or AWS_PROFILE) exists in ~/.aws/config. A missing one shows No AWS profile on the Clusters screen.

Expired sessions

When an SSO session expires, the cluster shows Log in. Click it: KubeDrive runs aws sso login for that profile and your browser asks you to confirm. One login renews every context that uses the same SSO session.

Accounts

KubeDrive shows the AWS account of each EKS cluster. Give an account a name (for example “Payments”) from the cluster’s pencil menu, and every cluster in it shows that name.