azure-aws-creds VS aws-vault

I use this myself with a few clients https://github.com/mr-olson/azure-aws-creds

Undying fondness for aws-vault to securely cache my session credentials.

you might want to check https://github.com/99designs/keyring and https://github.com/99designs/aws-vault

You install aws-vault (https://github.com/99designs/aws-vault), configure it according to the README and make sure you have an SSO entry that is compatible, i.e.:

I use a aws-vault to switch thought all profiles on all aws account. It support SSO with 2FA.

Nice! Do I understand this correctly?

You use aws-vault(https://github.com/99designs/aws-vault) and configure it with IAM and MFA with YubiKeys. You configure e.g. the profile jonsmith.

When you run

aws-vault exec jonsmith -- aws s3 ls

it will ask you, e.g. every hour to confirm with YubiKeys and cache the key for one hour. After that the temporary keys expire. Can you also store keys different from AWS?

Don't know about kube, but awscli and a few others decouple the idea of getting credentials and doing the actions. You can use the password every time, but a better way is to either use the preconfigured profile or some wrapper which does use the keychain. For example https://github.com/99designs/aws-vault/ supports one-off commands and shell sessions with pre-populated tokens.

It sounds like you have AWS SSO enabled and need a way to run scripts manually in the terminal. Take a look at the aws-vault project that makes it easy working with multiple AWS accounts.

A tool called aws-vault can fix the "insecure" part.

Take a look at aws-vault, which has support for SSO and running in a docker container.

I read the docs on: https://github.com/99designs/aws-vault