A wrapper for executing a command with AWS CLI v2 and SSO
This is a simple script to make it easier to use AWS Single Sign On credentials with tools that don't understand the
sso entries in an AWS profile.
The script provides the following capabilities:
- Running a specified command with the retrieved AWS SSO credentials.
- Exporting the AWS SSO credentials.
credential_processwithin an AWS profile
- Supporting assuming roles within an AWS profile
Please note that the script is called
aws2-wrap to show that it works with AWS CLI v2, even though the CLI tool is no longer called
pip3 install aws2-wrap==1.1.9
Run a command using AWS SSO credentials
aws2-wrap [--profile <awsprofilename>] [--exec] <command>
Note that if you are using
<command> contains spaces, it must be surrounded with double-quotation marks.
You can also specify the profile to be used via AWS_PROFILE which then allows the same profile to be used by subsequent tools and commands.
aws2-wrap --profile MySSOProfile terraform plan
aws2-wrap --profile MySSOProfile --exec "terraform plan"
AWS_PROFILE=MySSOProfile aws2-wrap terraform plan
If you are having problems with the user of quotes in the command, you may find one of the other methods works better for you.
Generate a temporary profile in the $AWS_CONFIG_FILE and $AWS_SHARED_CREDENTIALS_FILE file
There are some utilities which work better with the configuration files rather than the environment variables. For example, if you need to access more than one profile at a time.
aws2-wrap --generate --profile $AWS_PROFILE --credentialsfile $AWS_SHARED_CREDENTIALS_FILE --configfile $AWS_CONFIG_FILE --outprofile $DESTINATION_PROFILE
Export the credentials
There may be circumstances when it is easier/better to set the appropriate environment variables so that they can be re-used by any
Since the script cannot directly set the environment variables in the calling shell process, it is necessary to use the following syntax:
eval "$(aws2-wrap [--profile <awsprofilename>] --export)"
eval "$(aws2-wrap --profile MySSOProfile --export)"
If you are using PowerShell, the equivalent command is:
aws2-wrap --profile MySSOProfile --export | invoke-expression
Assuming a role via AWS SSO
.aws/config file can look like this:
[default] sso_start_url = xxxxxxxxxxxx sso_region = us-west-2 sso_account_id = xxxxxxxxxxxx sso_role_name = SSORoleName [profile account1] role_arn = arn:aws:iam::xxxxxxxxxxxx:role/role-to-be-assumed source_profile = default region = ap-northeast-1
allowing you to then run:
aws2-wrap --profile account1 <command>
<command> will be run under
Use the credentials via .aws/config
If you are using a tool that works with normal AWS credentials but doesn't understand the new AWS SSO credentials, another option is to add a profile to
.aws/config that calls the
For example, add the following block to
[profile Wrapped] credential_process = aws2-wrap --process --profile <awsprofilename>
then, after authentication, you can run any command that uses AWS credentials by specifying the "Wrapped" profile:
aws sso login --profile <awsprofilename> export AWS_PROFILE=Wrapped export AWS_SDK_LOAD_CONFIG=1 terraform plan
Note that because the profile is being specified via
AWS_PROFILE, it is sometimes necessary (as shown above) to set
AWS_SDK_LOAD_CONFIG in order to get tools like
terraform to successfully retrieve the credentials.
Thanks to @damian-bisignano, @flyinprogrammer, @abeluck, @topu, @bigwheel, @krabbit, @jscook2345, @hieki, @blazdivjak, @fukushun1994, @johann8384, @ppezoldt, @atwoodjw and @lummish for their contributions.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size aws2_wrap-1.1.9-py3-none-any.whl (19.5 kB)||File type Wheel||Python version py3||Upload date||Hashes View|
|Filename, size aws2-wrap-1.1.9.tar.gz (7.3 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for aws2_wrap-1.1.9-py3-none-any.whl