Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BB-233] No need to run configure sso more than once now #208

Merged
merged 1 commit into from
Feb 1, 2024
Merged

[BB-233] No need to run configure sso more than once now #208

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions docs/user-guide/ref-architecture-aws/features/sso/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,8 +73,6 @@ Once the project has been set up to use SSO, the profiles that AWS CLI will use

To do this, simply run `leverage aws configure sso`.

This step needs to be performed every time the user works in a new account that assumes a different role than the one that they are currently using. For example, if the user is working in the `security` account, assuming the `DevOps` role, but needs to operate on a layer of the `management` account which requires assuming an `Administrator` role, then SSO needs to be reconfigured.

!!! warning "Attention"
This step simply writes over the credentials files for AWS CLI without asking for confirmation from the user. So it's recommended to backup/wipe old credentials before executing this step in order to avoid loss of credentials or conflicts with profiles having similar names to the ones generated by Leverage.

Expand Down
Loading