Your workspace.
Every account. One window.
Open genuine AWS pages in separate persistent desktop sessions. Save your own IAM or root credentials locally, then complete sign-in and MFA with AWS.
1. Install CloudDock Desktop
Your operator supplies the Windows installer built for this CloudDock server. The development repository can build it with pnpm package:desktop. Public signed distribution is not configured in this checkout.
Start the app and sign into your CloudDock workspace. Device authorization is automatic. No extension or pairing code is required.
2. Save your own AWS login
Open Local vault inside the app. Create a master passphrase, choose your AWS account and save its IAM username/password or root email/password. Enable autofill if desired. CloudDock cannot recover your passphrase.
Passwords stay encrypted on this device. Other engineers configure their own vault entries.
3. Sign in from the dashboard
Choose Sign In. The real AWS website opens in its own desktop tab. When a supported form is available, the unlocked vault can fill it. Current AWS GET forms require a manual Sign In click. Root email steps may also require Next. AWS may require MFA or another authentication challenge.
Open another account without deliberately replacing the first identity’s cookies. Tabs reuse persisted site data after restart when AWS permits; CloudDock reports authentication as unknown.
The app still needs this CloudDock backend online. A hosted backend avoids running a development server on your laptop. Your vault starts locked after restart, but you do not need to pair the device each day.