You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 8, 2025. It is now read-only.
Create a AWS config file enumerating the configured accounts so that it can be downloaded and put in the correct location for my users. If it could be left in a well-known location on github I could update my configuration scripts to pull from that location, but generated it for the configured accounts and roles is what this issue is trying to capture. I think if enumerating all the possibilities and let the SSO sort out "if you allowed" access.
Create a AWS config file enumerating the configured accounts so that it can be downloaded and put in the correct location for my users. If it could be left in a well-known location on github I could update my configuration scripts to pull from that location, but generated it for the configured accounts and roles is what this issue is trying to capture. I think if enumerating all the possibilities and let the SSO sort out "if you allowed" access.
[default] region = us-east-1 [profile login] sso_start_url = https://missionfocus.awsapps.com/start sso_region = us-east-1 [profile missionfocus] sso_start_url = https://missionfocus.awsapps.com/start sso_region = us-east-1 sso_account_id = 909262413378 sso_role_name = AWSAdministratorAccess region = us-east-1 output = json [profile mf-oit] sso_start_url = https://missionfocus.awsapps.com/start sso_region = us-east-1 sso_account_id = 671094943849 sso_role_name = AWSAdministratorAccess region = us-east-1 output = json << etc >>