AWS Login SchedulerChrome extension · On the Chrome Web Store
Start your workday in the right AWS workspace — automatically.
AWS Login Scheduler is a Chrome extension that signs you in to the AWS console on the weekdays and time you choose, and opens the AWS service you use next.
For developers, DevOps engineers, freelancers and agencies who sign in to the same AWS accounts every morning. IAM user sign-in with optional TOTP MFA; credentials are encrypted on your device.
Available for Chrome. Firefox support is coming soon.
Stop repeating the same AWS login routine.
Every morning, the same five steps.
- Open AWS
- Find the right account
- Sign in
- Enter MFA
- Find the service you actually need
Configure it once. Let the extension handle the routine.
It is the same handful of clicks whether you look after one account or four — a production account, a staging account, a client's account. The work is not hard, it is just repeated.
Built for the AWS workflow you repeat every day.
What the current version does — nothing here is planned work.
Multiple AWS profiles
Keep up to 4 AWS profiles configured in the current version — each with its own account, IAM user and destination.
Scheduled login
Run profiles automatically on the weekdays and time you choose, or trigger one immediately with Run Now.
Timezone support
Schedules use the timezone saved with each profile, so 09:00 keeps its meaning if your machine's zone changes.
TOTP MFA
Authenticator-based TOTP codes when the AWS account requires MFA. Codes are generated on your device.
Choose your destination
Land on the AWS service you actually work in after a successful login — with a region where the console needs one.
Existing session control
Decide per profile whether an AWS session already open in the browser is preserved or replaced.
Set it once. Let it run.
Four steps in the extension popup. There is no account to create.
Add your AWS profile
Name it, then give it the AWS account ID or alias and the IAM username you sign in with.
Configure the schedule
Pick the weekdays, the time — 09:00 by default — and the timezone the schedule should be read in.
Choose MFA and destination
Add an authenticator if the account requires TOTP, then choose the AWS page the run should open.
Let the extension handle the login
At the scheduled moment it signs in, confirms the session belongs to the account your profile names, and opens your destination.
Automation happens in the browser. Your AWS credentials remain local to the extension — read how credentials are handled before you decide what to trust it with.
Your AWS credentials stay on your device.
The extension is the only thing that ever touches them. This website has no part in it.
- AWS credentials are handled locally by the extension. They are never sent to this website — there is no server, no analytics and no telemetry to send them to.
- TOTP secrets never leave your device. Codes are generated there, and a QR image you upload is decoded there.
- Scheduler and execution records carry no passwords and no TOTP secrets. A run trail records host and path only — never a query string, never a value the extension filled in.
- Your password and authenticator secret are encrypted on your device and protected by a passphrase you choose. The passphrase is never stored anywhere.
- You unlock the vault once per browser session — after Chrome starts or the extension reloads. A run due before that does not start; it reports that the vault was locked and leaves your schedule in place.
- The website is separate from the local credential vault, and stays that way as the dashboard is built.
Where the encryption stops
It protects the saved data at rest — a copied Chrome profile directory or a disk backup contains only ciphertext. It does not protect against malware, a compromised operating system, a program running as your operating-system user while the vault is unlocked, or anyone who knows your passphrase. And because the passphrase is never stored, it cannot be recovered: if you forget it, you will need to set up a new vault and enter your credentials again.
Whatever you trust it with, use a dedicated IAM user with the least access that makes your work possible — never a root or administrator account. What the extension stores, and why nothing is transmitted, is set out in the privacy policy.
One browser. Multiple AWS profiles.
Up to 4 profiles in this version. Each one is independent: its own account, its own IAM user, its own destination and its own schedule.
Production
Mon-Fri · 09:00
EC2 · ap-south-1
Staging
Mon-Fri · 09:05
CloudWatch · ap-south-1
Development
Mon-Fri · 09:10
ECS · ap-south-1
Client
Mon-Thu · 09:15
S3
Enable, disable or reschedule one profile without touching the others. The names are labels you chose, nothing more. The extension signs in as the IAM user you gave it — it does not change permissions, roles or IAM policy — and it stops rather than continuing if the session it gets back belongs to a different account than the profile names.
Keep working in Chrome while the login runs.
Designed for background-tab operation, so a scheduled sign-in does not require you to keep the AWS tab in focus. Nothing steals focus mid-run, and the run never adopts a tab you opened — it opens its own and never closes one.
Being honest about the edges: Chrome cannot wake a sleeping machine, so a run due while the laptop is shut happens on wake, and is skipped and reported rather than signing you in hours after you wanted it. One profile signs in at a time. Background-tab behaviour is under active real-browser testing.
- Runs hiddenOrchestration lives in the extension's service worker, not in the popup — closing the popup does not interrupt anything.
- Waits on evidenceA hidden tab is given more time only while it is still making progress, so a genuinely stuck run still fails fast instead of hanging.
- Leaves a trailEvery run — successful or not — records a redacted account of what happened, so “it worked while I wasn't looking” is something you can check rather than assume.
Free on the Chrome Web Store
Ready to stop doing the same login every morning?
Install AWS Login Scheduler from the Chrome Web Store. Read how credentials are handled first — that is the part worth knowing before you hand anything an AWS password.
- Choose Add to Chrome on the listing, then pin the extension's toolbar icon.
- Open it and add a profile: AWS account ID or alias, IAM username, password, destination and schedule.
- On your first save, create a vault passphrase. It encrypts your credentials and is never stored.
- After each Chrome start, unlock the vault once so scheduled runs can sign in.
Chrome only for now. AWS IAM Identity Center (SSO), team accounts and credential sync are not part of this version. Use a dedicated IAM user with the least access you need — never a root or administrator account.
Questions people ask first.
What is AWS Login Scheduler?
A Chrome extension that signs in to the AWS console at a time you choose and opens the AWS page you actually work in, rather than the account landing page. It is an independent product, available free on the Chrome Web Store.
How do I install AWS Login Scheduler?
Open the AWS Login Scheduler listing on the Chrome Web Store and choose Add to Chrome. Pin the toolbar icon, open it, and add your first profile. The first time you save one, the extension asks you to create a vault passphrase.
How do I schedule an AWS console login?
In the extension popup, add a profile with the AWS account ID or alias and your IAM username, then pick the weekdays, a time (09:00 by default) and the timezone the schedule is read in. Scheduling is Monday to Friday. At that time the extension signs in and opens the destination you chose; Run Now does the same thing immediately.
Does it support MFA and TOTP?
Yes, for authenticator-app (TOTP) codes. Add the authenticator by uploading its QR image, pasting an otpauth:// link, or typing the setup key; the image is decoded on your device and the codes are generated there. Passkeys and FIDO2 security keys cannot be automated, so an account that requires one is not a fit.
Does AWS Login Scheduler support every AWS sign-in method?
No. It automates IAM user sign-in: account ID or alias, IAM username, password, and an optional authenticator-app code. AWS IAM Identity Center (SSO), federated sign-in and passkey or security-key MFA are not supported. It is meant for a dedicated, least-privilege IAM user — never the root user or an administrator.
Does it support multiple AWS accounts?
Yes — up to 4 profiles in this version, each with its own account, IAM user, destination and schedule. One profile signs in at a time.
Can I choose which AWS service opens?
Yes. Pick a destination per profile — the console home, EC2, S3, RDS, ECS, Lambda, CloudWatch, IAM, DynamoDB and others — plus a region for the consoles that are region-scoped.
Can I schedule different times for different profiles?
Yes. Days, time and timezone are stored per profile, so a staging profile can run five minutes after a production one.
How are my stored AWS credentials protected?
Your password and authenticator secret are encrypted on your device and protected by a vault passphrase you choose. Only the encrypted form is saved. This protects the saved data at rest; it does not protect against malware, a compromised operating system, an unlocked vault on an accessible device, or a weak or compromised passphrase.
Is my vault passphrase stored or transmitted?
No. The passphrase is never stored, never sent anywhere. If you forget your passphrase, your saved credentials cannot be recovered. You will need to set up a new vault and enter your AWS credentials again. It must be at least 12 characters.
Do I need to unlock the vault after restarting my browser?
Yes. After Chrome starts or the extension reloads, the vault is locked until you enter your passphrase once. While it stays unlocked, scheduled runs work without you present.
What happens if the vault is locked when a scheduled login is due?
The run does not start. No tab opens, nothing is sent to AWS, no retry is armed, and the extension reports that the vault was locked. The schedule stays configured, and unlocking within 60 minutes of the scheduled time lets that run still go.
What happens if my computer is asleep at the scheduled time?
Chrome cannot wake a sleeping or powered-off machine, so the run happens when it wakes. If that is more than 60 minutes after the scheduled time, the run is skipped and reported instead of signing you in hours late.
Does it work if I switch to another browser tab?
It is designed for it. A backgrounded AWS tab is a supported state rather than a user error, and every run keeps a redacted trail so you can confirm what happened while you were not watching.
Does the extension send my AWS password to the website?
No. There is no server to send it to — no account, no analytics, no telemetry. Credentials stay in the extension's storage on your device, and the only network activity is your browser's own sign-in request to Amazon.
Is AWS Login Scheduler available for Firefox?
Not yet. Firefox support is coming soon, but the extension has not been released on Firefox Add-ons and no Firefox build is available. Today it is available for Chrome only.
Is it officially made by AWS?
No. AWS Login Scheduler is an independent third-party product and is not affiliated with or endorsed by Amazon Web Services.