Saved profiles and recent connections
Reconnect in one click. Save Quick Connect, Assume Role and SSO configurations under a name, and pick up where you left off from the automatic recent list.
Overview
The Saved Profiles tab on the login screen has two lists. Recent Connections is filled automatically after every successful connection. Saved Profiles holds the configurations you chose to keep by ticking Save this connection or Save profile on one of the method tabs. Clicking a row in either list connects immediately; there is no extra button to press.
Recent connections
The five most recent connections are kept, newest first, and de-duplicated by identity (region, profile and endpoint for Quick Connect; role ARN for Assume Role; start URL, account and role for SSO). Each row is titled by its method and shows a one-line summary.
| Row title | Summary line |
|---|---|
| ⚡ Quick Connect | <region> · <profile> |
| 🛡️ Assume Role | <region> · <role name> |
| 🌐 AWS SSO | <region> · <account> / <role> |
Saving a profile
- On Quick Connect, tick Save this connection and type a Profile Name such as “My Prod DB”. The profile is saved right before the connection attempt.
- On Assume Role, tick Save profile. The ARN, session name, region, local profile and environment tag are stored.
- On AWS SSO, tick Save profile in the account and role step. The start URL, SSO region, DynamoDB region, account and role are stored.
Saving with a name that already exists replaces the previous profile. To remove one, hover its row in the Saved Profiles list and click the 🗑 button that appears, then confirm. There is no limit to how many profiles you can keep.
Using a saved profile
- Quick Connect profile — connects directly and restores the environment tag.
- Assume Role profile — runs AssumeRole immediately with the saved ARN, session name, region and local profile.
- SSO profile — switches to the AWS SSO tab and runs the whole sign-in. If a cached SSO token is still valid, the browser is not opened and the saved account and role are selected for you.
Any failure surfaces as a toast with the AWS error message, and you stay on the login screen.