|
|
|
|
|
|
by conradludgate
1696 days ago
|
|
|
As others have mentioned, there is saml2aws. I make use of this, with aws profiles and with saml2aws configured as a 'credentials provider' in aws. If I have already entered my username, password and MFA code once in a session, all my other profiles become active. I can use `aws --profile eks-dev` for instance to connect to that configured account/role. This extends well to my kubeconfig which make use of these specified profiles to login. So I just run saml2aws, and my kubectl contexts also automatically get configured |
|
|