dnxsso 0.5.0

Sync up AWS CLI v2 SSO login session to legacy CLI v1 credentials

dnxsso

Yet Another AWS SSO - sync up AWS CLI v2 SSO login session to legacy CLI v1 credentials.

Do I need it?

• See https://github.com/DNXLabs/dnxsso/wiki

Prerequisite

• Required AWS CLI v2
• Assume you have already setup AWS SSO for your organization

TL;DR

• Install latest from PyPI like so:

pip install dnxsso

• Do your per normal SSO login and, have at least one org-level SSO login session cache:

aws sso login --profile=dev

• To sync for all named profiles (e.g. dev, prod, stag, ...), then just:

dnxsso

• To sync default profile and all named profiles, do:

dnxsso --default

• To sync default profile only, do:

dnxsso --default-only

• To sync for selected named profile, do:

dnxsso -p dev

• To sync for multiple selected named profiles, do:

dnxsso -p dev prod

• To sync for default profile as well as multiple selected named profiles, do:

dnxsso --default -p dev prod

• To sync for all named profiles start with prefix pattern lab*, do:

(zsh)
dnxsso -p 'lab*'

(bash)
dnxsso -p lab*

• To sync for all named profiles start with prefix pattern lab* as well as dev and prod, do:

dnxsso -p 'lab*' dev prod

• Use -e flag if you want a temporary copy-paste-able time-gated access token for an instance or external machine. It use default profile if no additional arguments pass. The main use case is for those who use default profile, and would like to PIPE like this aws sso login && dnxsso -e | pbcopy. Otherwise for named profile, do dnxsso -e -p dev.

  PLEASE USE THIS FEATURE WITH CARE SINCE ENVIRONMENT VARIABLES USED ON SHARED SYSTEMS CAN GIVE UNAUTHORIZED ACCESS TO PRIVATE RESOURCES:

dnxsso -e
export AWS_ACCESS_KEY_ID=xxx
export AWS_SECRET_ACCESS_KEY=xxx
export AWS_SESSION_TOKEN=xxx

• You can also use dnxsso subcommand login to SSO login then sync all in one go:

dnxsso login -h
dnxsso login
dnxsso login -e
dnxsso login --this
dnxsso login --profile dev
dnxsso login --profile dev --this

• Print help to see other options:

dnxsso -h

• Then, continue per normal with your daily tools. i.e.
  • cdk deploy ...
  • terraform ...
  • cw ls -p dev groups
  • awsbw -L -P dev

Develop

• Create virtual environment, activate it and then:

make install
make test
python -m dnxsso --trace version

• Create issue or pull request welcome

License

MIT License