Every AWS identity.
Its own place in Firefox.
One browser, separate account cookies and an optional encrypted local credential vault. The AWS Console stays on AWS.
1. Install the extension
Use desktop Firefox 142 or later. Your operator must distribute a Mozilla-signed extension for permanent installation. A signed public download is not available from this development checkout.
For local testing, build the extension from the repository, then open about:debugging#/runtime/this-firefox, choose Load Temporary Add-on and select apps/firefox-extension/dist/manifest.json. Allow access to the configured CloudDock site and AWS sign-in hosts.
Temporary installations are removed when Firefox closes. Permanent session/update testing needs a signed build or the documented web-ext test profile.
2. Create and pair your vault
Open the extension, create a master passphrase of at least 14 characters and keep it safe. There is no CloudDock recovery key.
Choose Generate pairing code. Approve that code in Extension & Devices in this workspace. Keep extension settings open until pairing completes.
Each engineer pairs their own Firefox and saves their own AWS credentials. A pairing expires after 30 days or when revoked.
3. Save your IAM identity and Sign In
In the extension directory choose Manage login, add your IAM identity, and enter its username and password in the extension-owned vault editor. Enable autofill explicitly. No AWS password is entered in this website.
Return to the dashboard and choose Sign In. The server authorizes a one-time launch; Firefox opens the matching container. Supported IAM pages can receive your saved login while the vault is unlocked. Check the account ID, choose Sign in on AWS when required, and complete MFA normally.
The live AWS OAuth IAM form currently uses GET with JavaScript handling. CloudDock fills verified fields but deliberately leaves submission to you on that layout. Unknown pages, CAPTCHA, MFA and root-account forms do not receive saved credentials. An opened tab never proves that you are authenticated.
Vault keys stay in background memory and lock after 10 minutes without interaction, browser restart or Firefox background suspension. Containers persist independently of the vault. Clean them up only from extension settings after closing their tabs.