Improved IAM user credential support
Read our guide on this feature here.
This release adds support for storing IAM user credentials in secure storage with Granted (#254).
Previously, if you were using an IAM user credentials with Granted, you'd need to store them in plaintext in ~/.aws/credentials. Now, running
granted credentials import <profile name>
will import the user credentials to your system's keychain and remove the plaintext.
A big thanks to @ipmb and @eugene1g for their feature request and feedback on the feature in #178.
As part of #254 we have migrated the name of the Keyring service which stores SSO tokens from granted to granted-aws-sso-tokens. We plan on using this suffix format to store different kinds of credentials in secure storage. When storing AWS IAM user credentials, Granted uses granted-aws-iam-credentials as the Keyring service name.
Because of this change, when upgrading to v0.4.0 you may see a keychain prompt on MacOS similar to the below. You will also need to authenticate again to AWS SSO after upgrading.
New AWS service shortcuts
This release adds additional shortcuts for networking services on AWS.
assume -s vpc # opens a console to the VPC service
assume -s dx # opens a console to the AWS Direct Connect service
A big thanks to @networkprogrammer for contributing these shortcuts.
What's Changed
- update wording of SSO command by @chrnorm in #278
- Update assumer_aws_sso.go by @jordiup in #276
- Added vpc and directconnect services by @networkprogrammer in #279
- granted credentials commands for securely storing IAM user credentials by @meyerjrr in #254
- fix Go syntax errors by @chrnorm in #282
New Contributors
- @networkprogrammer made their first contribution in #279
Full Changelog: v0.3.1...v0.4.0