How Can I Simplify K9s Usage with Multiple AWS Accounts and EKS Clusters via SSO?

Have you checked out Teleport? We're currently evaluating it, and it has a community version that might be worth trying out! It could simplify your access across multiple clusters.

I recommend checking out Granted.dev! It’s a tool I use to quickly change SSO roles in my CLI. It’s pretty straightforward and has made my life easier when switching contexts.

Why not use an identity provider like Okta for your EKS clusters? You could use kube-login locally to simplify the authentication process.

If you're using SSO, you can set up a distinct context for every cluster. There's an AWS CLI command for that, and in K9s, just type `: context` to select your desired context! Super easy once everything's set up!

You might also want to look into InfraHQ. It seems to have some useful features, but make sure to check it out and see if it's what you need: [InfraHQ](https://github.com/infrahq/infra)

You should give the AWS CLI SSO a shot! It lets you log into multiple AWS accounts and roles all at once instead of using individual credentials. Just configure your .aws/config like this, and you'll be good to go:
```
[profile login]
sso_start_url=https://d-xxxxxxx.awsapps.com/start
sso_region=us-east-1
sso_account_id=none
sso_role_name=none

[profile ]
sso_account_id=xxxxxxxxxx
sso_role_name=myRole
sso_start_url=https://d-xxxxxxx.awsapps.com/start
sso_region=us-east-1
```
Log in with `aws sso login --profile login` and then update kubeconfig for each cluster with `aws eks update-kubeconfig --profile --region --name `. Just switch between clusters in K9s using `:ctx`. It makes the process flow much smoother!

I found this helpful post about using SSO to manage clusters. It provides a step-by-step guide on how to streamline switching contexts. Once the setup is done, you just run `kubectl config use-context cluster1` or `cluster2`, and you're good! Here's the link: [link](https://medium.com/@mrethers/authenticating-to-eks-clusters-with-aws-sso-like-a-boss-too-4ba100c87f0b)