gimme-aws-creds VS saml2aws

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.

related: message on saml2aws repo

If you have an external identity provider, you can add a SAML provider in IAM and use saml2aws locally. The session duration can be configured on the role.

Or if you have an existing IdP you can use https://github.com/Versent/saml2aws and https://github.com/makethunder/awsudo. By setting up a central account that you put in your trust policy which users can assume roles.

In my company everything goes through Active Directory and we use saml2aws [1] to generate credentials with two factor involved. It works quite well for us. We even use this for our artists to create local builds of our games since we keep all important secrets and such in aws secrets mananger. We scope access to said secrets with custom roles and tags.

[1] https://github.com/Versent/saml2aws

Technically I guess it should be possible with something like saml2aws, but it doesn't support AWS as an IdP yet.

saml2aws-multi is a simple tool I created for using saml2aws more effectively on day-to-day tasks. saml2aws-multi provides an easy-to-use command line interface to support login and retrieve AWS temporary credentials for multiple roles of different accounts with saml2aws.