Do not assume AWS is down simply because you cannot sign in.
Check the official AWS Health Dashboard first for a current AWS service event.
If AWS is not reporting a relevant incident, identify whether you are using a root user, IAM user, IAM Identity Center, federated login, or the newer AWS sign-in experience.
The exact error message matters. Password, MFA, browser-session, device-time and organization-policy problems require different fixes.
If multiple unrelated AWS services suddenly fail at the same time, check AWS Health before changing your credentials.

Status can change quickly. Use the official AWS Health Dashboard for the current service state.

Check Official AWS Status

Quick Answer

AWS Sign-In not working? First check AWS Health to rule out a service incident.
“It’s not you, it’s us”: AWS recommends checking your device’s date and time and enabling automatic time synchronization.
“An unexpected error has occurred” with an authenticator: synchronize the authenticator device’s clock.
Password rejected: check Caps Lock and make sure you are not entering an older password.
AWS Console page won’t open: a firewall or web filter may be blocking AWS sign-in domains.
IAM user MFA problem: contact your AWS administrator if you cannot use another registered MFA device.

AWS Sign-In not working today does not necessarily mean Amazon Web Services is experiencing an outage. AWS login problems can originate from the AWS service itself, incorrect credentials, MFA synchronization, the wrong login page, a corporate identity provider, network restrictions or browser sessions.

The fastest way to diagnose the problem is to check AWS service status first and then match the exact error message on your screen with the appropriate troubleshooting method below.

Is AWS Sign-In Down Today?

If AWS suddenly stops accepting your login, particularly when other AWS services are behaving abnormally, check the official AWS Health Dashboard before resetting passwords or modifying your computer.

The dashboard is the authoritative location for AWS service-health information:

AWS Health Dashboard

Remember that an AWS incident can be service-specific or regional. A problem affecting one AWS service or Region does not automatically mean every AWS customer is unable to sign in.

Also Read : SECURE 2.0 Catch-Up Adjustments

What You See	Likely Area to Check	First Action
AWS login suddenly unavailable	AWS service status	Check AWS Health
“It’s not you, it’s us”	Device time / sign-in configuration	Synchronize date and time
Password isn’t working	Credentials	Check Caps Lock and password version
Authenticator unexpected error	TOTP/MFA synchronization	Synchronize authenticator device time
AWS login page won’t load	Firewall/network filtering	Check AWS sign-in domains
Authentication failed from one network	Organization sign-in policy	Contact administrator

Why Is AWS Sign-In Not Working?

There is no single cause for every AWS login failure. Before applying a fix, determine how you normally access AWS.

AWS account root user
IAM user
IAM Identity Center
Federated corporate identity
New AWS sign-in experience

This matters because AWS gives different recovery instructions for each identity type.

Fix 1: Check the AWS Health Dashboard

This should be your first step whenever AWS Sign-In suddenly stops working for no obvious reason.

Open the official AWS Health Dashboard.
Look for active operational issues.
Check whether the affected AWS service or Region is mentioned.
If AWS confirms a relevant incident, monitor AWS’s updates rather than repeatedly changing your password or MFA configuration.

Useful diagnostic clue: If colleagues or users in different locations begin reporting the same AWS problem at approximately the same time, investigate service status before assuming the problem is specific to your account.

Fix 2: AWS Says “It’s Not You, It’s Us”

AWS specifically documents the message “It’s not you, it’s us” in its sign-in troubleshooting guidance.

For the newer AWS sign-in experience, AWS recommends checking the date and time settings on the device being used to sign in.

On Windows

Open Settings.
Select Time & language.
Select Date & time.
Enable Set time automatically.
Enable the correct time zone setting where appropriate.
Try AWS Sign-In again.

AWS recommends synchronization with a known Network Time Protocol (NTP) server when automatic time configuration is unavailable.

AWS also advises checking the formatting of the email address when this message appears in its newer sign-in experience.

Fix 3: AWS Password Isn’t Working

If AWS accepts your email or username but rejects the password, don’t immediately assume that the account has been compromised.

AWS recommends checking two simple things first:

Make sure Caps Lock is off.
Make sure you aren’t entering an older password.

If the current password is definitely being entered correctly and still isn’t accepted, follow AWS’s password-reset procedure for your account type.

Important: Root users, IAM users and IAM Identity Center users do not necessarily use the same password-recovery process. Identify the account type before resetting anything.

Fix 4: “An Unexpected Error Has Occurred” With AWS MFA

This is one of the more useful errors to diagnose because AWS provides a specific explanation for the authenticator scenario.

Time-based one-time passwords (TOTP) rely on the AWS server and your authenticator device having synchronized clocks.

If you receive “An unexpected error has occurred” while registering or signing in with an authenticator application:

Open your phone’s Date & Time settings.
Enable automatic date and time.
Enable automatic time-zone detection if appropriate.
Close and reopen the authenticator app.
Generate a fresh authentication code.
Try AWS Sign-In again.

If automatic synchronization isn’t available, AWS recommends synchronizing the device against a reliable time source.

Fix 5: AWS MFA Device Is Lost or Not Working

The correct recovery method depends on your AWS identity.

IAM User

If you are an IAM user and another MFA device is registered to your user, try that device.

If you cannot recover the MFA device yourself, AWS says IAM users should contact their administrator. The administrator can deactivate an MFA device that is no longer working.

Root User

For a root user, try another MFA device registered to the same root user if one is available. AWS also provides a specific MFA recovery process for root-user access.

If recovery is impossible through the available methods, use AWS Support.

Fix 6: AWS Management Console Login Page Won’t Open

If the AWS sign-in page itself won’t load, the problem may be outside your AWS account.

AWS specifically notes that a firewall or web-content filter may prevent access to its sign-in pages.

For root and IAM users, AWS identifies this domain pattern:

*.signin.aws.amazon.com

IAM Identity Center and certain first-party application sign-ins may also require AWS sign-in and awsapps.com endpoints.

If you are on a corporate, school or tightly controlled network, ask the network administrator to verify that required AWS domains are not being blocked.

Do not disable corporate security controls yourself. If an organization manages your network, ask its administrator to review the required AWS endpoints.

Fix 7: Make Sure You’re Using the Correct AWS Login Page

AWS documents incorrect sign-in pages as another reason valid credentials can appear not to work.

For example, someone trying to use root-user credentials should not assume those credentials belong in an IAM-user sign-in workflow.

Likewise, enterprise users may normally authenticate through an organization’s AWS access portal rather than directly with ordinary AWS account credentials.

If you normally use single sign-on, look for your organization’s AWS access portal URL. AWS notes that these URLs can contain:

awsapps.com/start

or the AWS sign-in platform.

Fix 8: “Authentication Failed” or “Sign In From a Different Network”

This error deserves special attention because switching passwords may accomplish nothing.

AWS organizations can use sign-in resource-based policies or resource control policies that restrict sign-in according to network conditions.

AWS documents messages including:

Your authentication information is incorrect. Please try again.
Authentication failed Invalid request.
Authentication failed: To access this account, sign in from a different network, or contact your administrator for more information.

If the message specifically refers to another network or organizational access requirements, contact the AWS administrator responsible for the account instead of repeatedly resetting your password.

Fix 9: AWS IAM Identity Center “It’s Not You, It’s Us”

For IAM Identity Center, the same wording can have a more specific organizational cause.

AWS says the error can indicate a setup problem with the IAM Identity Center instance or its external identity provider (IdP).

Administrators may need to verify:

Device date and time.
The identity-provider certificate configured in IAM Identity Center.
SAML metadata configuration.
AD Connector service-account credentials, where applicable.

These are administrator-level troubleshooting steps. Ordinary users should contact their organization’s IT or AWS administrator rather than changing identity-provider configuration themselves.

Fix 10: AWS Sign-Out Doesn’t Completely Sign You Out

Sometimes the problem isn’t signing in—it is getting rid of an old AWS session.

AWS says sign-out is designed to occur immediately, but full sign-out may take up to an hour in its newer sign-in experience.

If AWS keeps asking you to choose an account, you may have multiple active sessions in the browser.

These can include:

AWS Builder ID sessions.
AWS account sessions.
Project-account sessions.

Select the intended account and sign out of unused active sessions when finished.

AWS Sign-In Error Diagnosis Table

AWS Problem	Check First	Recommended Action
AWS appears down	AWS Health	Check official service status
It’s not you, it’s us	Device clock	Enable automatic time synchronization
Password rejected	Caps Lock / old password	Verify password or use correct recovery procedure
MFA unexpected error	Authenticator clock	Synchronize device time
Lost IAM MFA	Other registered MFA device	Use it or contact administrator
Console page won’t load	Firewall/filter	Verify AWS sign-in domains are allowed
Wrong network error	Organization policy	Contact AWS administrator

What Should You Avoid Doing?

Random troubleshooting can make an AWS access problem more difficult to diagnose.

Do not repeatedly change your password if AWS has confirmed a service incident.
Do not remove a working MFA device unless you understand your recovery options.
Do not disable corporate firewall or security policies without authorization.
Do not share AWS passwords, MFA codes, access keys or secret keys with anyone offering an unofficial “fix.”
Do not assume a Google search result claiming “AWS is down” represents official AWS status.
Do not confuse an Amazon.com shopping-account login issue with an AWS account problem.

When Should You Contact AWS Support?

Contact AWS Support when the documented recovery procedures don’t restore access, particularly for root-account access or MFA recovery.

AWS notes that Support cannot discuss details of an AWS account other than the account you are signed into and cannot simply change account credentials on request.

AWS also states that it does not publish a direct phone number for reaching a support representative about these sign-in issues.

AWS Official Sign-In Troubleshooting

Official AWS Resources

For accuracy, use AWS’s own documentation when troubleshooting account-access problems:

Related Troubleshooting Guides

For additional service-status and login troubleshooting, see:

Editorial note: Replace or remove an internal link if the destination does not exist on your website. Do not create a broken internal link simply for SEO.

AWS Sign-In Not Working: Quick Answers

Quick Answer — What to Do Now

Check AWS Health first to determine whether AWS is reporting a relevant service incident.
If you see “It’s not you, it’s us,” check and automatically synchronize the device’s date and time.
If an authenticator produces “An unexpected error has occurred,” synchronize the authenticator device’s clock and generate a fresh code.
If your password isn’t working, verify Caps Lock and make sure you aren’t using an older password.
If the AWS login page won’t open, check whether your firewall or network filter is blocking AWS sign-in endpoints.
If you’re an IAM user with a broken or lost MFA device, contact your AWS administrator if another registered MFA device isn’t available.
If the error mentions network restrictions or authentication policy, contact your organization’s administrator.
For persistent account-access problems, follow AWS’s official recovery and Support procedures rather than using unofficial credential-recovery services.

Last reviewed: September 22, 2026. This article was checked against current AWS Sign-In documentation. Service status can change at any time; use the AWS Health Dashboard for current operational information.

AWS Sign-In Not Working Today? Login Error & Status