aws-mfa VS gimme-aws-creds

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.

I got gimme-aws-creds (https://github.com/Nike-Inc/gimme-aws-creds) to authenticate via Okta - but no AWS roles are found in the SAML response. It works fine through the AWS console.

Gimme creds works nicely: https://github.com/Nike-Inc/gimme-aws-creds

AWS has always lagged behind is offering reasonable native authentication options to its console and CLI. In order to support something like "yubikey" you need to go with another authentication and authorization provider such as Okta which provides support for a wide variety of MFA options. Then you can also use open source tooling such as https://github.com/Nike-Inc/gimme-aws-creds to grab temporary credentials. Okta is the one I'm most familiar but there are others out there as well.