Named profiles
AWS named profiles let the AWS CLI, SDKs and other tools use different credentials side by side. They live in ~/.aws/credentials, and the one called default is used when no profile is given.
Every Freeleapp session writes its temporary credentials to its own named profile, so you can have several sessions active at the same time:
aws s3 ls --profile productionAWS_PROFILE=staging terraform planCreate a profile
Section titled “Create a profile”- Settings › Profiles: type the name and click +.
- While creating a session: pick a profile from the list or type a new one.
- From the session menu: right-click a session, choose Change › Named Profile, and pick or add one.
A profile belongs to one session at a time: if you pick a profile another session already uses, Freeleapp tells you which one and keeps the current profile. Type a new name instead. New sessions get default suggested only while it exists and no other session uses it.
IAM Identity Center roles
Section titled “IAM Identity Center roles”Each role synced from IAM Identity Center gets its own profile, named <account>-<role>, for example payments-prod-AdministratorAccess (spaces become -). If another session already uses that name, a number is added: payments-prod-AdministratorAccess-2. You can still switch any role to another profile with Change › Named Profile.
Manage profiles
Section titled “Manage profiles”Settings › Profiles lists default and the profiles you added, to rename or delete them. The profiles sessions have of their own (<account>-<role>, or the session name for other sessions) are not listed there: they show in the session list, change with Change › Named Profile, and are deleted with their session.
When you delete a profile, Freeleapp lists the sessions that use it and moves each one to a profile of its own. default can be deleted too, and added again by typing default.