Authentication issues reported for AWS IAM Identity Center

Connectivity

Authentication issues reported for AWS IAM Identity Center

Amazon Web Services is investigating login failures and connectivity issues originating in its US-EAST-1 region. These problems affect the IAM Identity Center, which manages user access to various AWS accounts and business applications.

All news
Connectivity
16 November 2026

What this means for your business

If your business uses AWS for cloud hosting or integrated software, staff may be unable to sign in to their consoles or connected services. There is currently no workaround, and you should monitor internal support requests until Amazon restores service.

Current status of AWS connectivity

Amazon Web Services (AWS) has reported a service disruption affecting the US-EAST-1 region, which is located in Northern Virginia. While this region is physically distant from the UK, it often handles global functions for AWS services, including identity management and account sign-ups.

AWS has confirmed that users are experiencing errors when attempting to authenticate via the IAM Identity Center. This is the service that allows employees to use a single set of credentials to log into multiple AWS accounts or business applications.

Technical impact

The disruption specifically affects IAM Identity Center sign-in requests and the process for creating new AWS accounts. Any service that relies on this identity provider for verification is currently prone to errors.

AWS noted that for Kiro users, logins performed via social sign-in methods remain functional. However, for standard corporate logins managed through the AWS identity portal, there are no available workarounds at this time. Businesses must wait for Amazon's engineers to resolve the underlying connectivity issue.

What this means for UK businesses

Many UK small and medium businesses use AWS to host their websites, databases, or internal software. Even if your data is stored in the London region, the login process often routes through these global authentication systems.

If your technical team or staff report that they cannot access the AWS Management Console or that integrated third-party tools are failing to log in, this outage is the likely cause. We recommend that administrators avoid making significant configuration changes until the authentication service is stable to prevent being locked out of systems mid-task.

We will continue to monitor the AWS Service Health Dashboard for updates on a resolution.

Is your broadband and phone line ready?

Business connectivity and phones, with one number to call when something goes wrong.

Connectivity and phones

Not sure how exposed you are?

Twenty minutes on a call is usually enough to tell you.