aws-mfa VS aws-vault

I will tell you that some tools like sceptre and terraform barf using a profile with mfa like this and I ended up using aws-mfa: https://github.com/broamski/aws-mfa and run this for example to create a "dynamic" runamok-power profile:

I use MFA so store a long term key that is used to generate a temporary key. I use this tool to do the mfa: https://github.com/broamski/aws-mfa

I too, struggled with aws-vault and eventually gave up and use https://github.com/broamski/aws-mfa. If you want to take it one step further you can use oathtool and store the totp key in the encrypted vault of your choice. That is still MFA but if you store the factors on the same system you will need to decide about that risk before going the oathtool route.

The built in CLI MFA solution sucks if you have a workflow that relies on named profiles. We use them heavily at work and implemented aws-mfa to make it so that all of our stuff could work without adopting ridiculous workflows.

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