-
Notifications
You must be signed in to change notification settings - Fork 4
Support Named Profiles Instead of Default Profile #7
Description
What Happens
When the AWS SSO session is active, the credentials are always associated with the default profile. This makes it difficult to work with multiple AWS accounts using named profiles.
Expected Behavior
It should be possible to specify a named profile and have the credentials applied to that profile instead of default.
Why this is Important
The primary use case of awsesh is managing multiple AWS accounts, which typically involves named profiles.
Without named profile support, switching between accounts becomes cumbersome, requiring manual credential management.
Suggested Solution
Allow specifying a named profile when running awsesh (e.g., sesh $profilename).
Ensure credentials are stored and used under that profile instead of default.
Steps to Reproduce
Authenticate with sesh $profilename.
Run aws configure list.
Observe that credentials are applied to the default profile instead of $profilename.
Would love to see this enhancement! Let me know if I can help with any testing. 🚀