My company has a funny setup where we have SECRET and ACCESS_KEY only for one account. Then that account is configured to allow role assumption for a set of different accounts.
Also, it is a requirement that every user has MFA configured.
This tool does not seem to support adding environments that works with role assumption and MFA, although the aws-cli does.
As you can see, I don't have secret and access key for dev, qa, stg or prod. That makes this tool unusable for a lot of companies that are using this setup.
My company has a funny setup where we have SECRET and ACCESS_KEY only for one account. Then that account is configured to allow role assumption for a set of different accounts.
Also, it is a requirement that every user has MFA configured.
This tool does not seem to support adding environments that works with role assumption and MFA, although the aws-cli does.
My .aws/credentials looks something like:
More info:
https://aws.amazon.com/blogs/security/how-to-use-a-single-iam-user-to-easily-access-all-your-accounts-by-using-the-aws-cli/ https://docs.aws.amazon.com/cli/latest/userguide/cli-roles.html
As you can see, I don't have secret and access key for dev, qa, stg or prod. That makes this tool unusable for a lot of companies that are using this setup.