Updated 2026-11-15: AWS has marked the incident resolved. Its notice, "Service is operating normally: [RESOLVED] Increased Connectivity issues in US-EAST-1", was posted at 06:53 PST (20:23 IST) on the AWS Health Dashboard feed: https://status.aws.amazon.com/rss/all.rss
AWS says it experienced connectivity issues in the US-EAST-1 Region on 15 November 2026 that affected IAM Identity Center sign-in requests and AWS sign-ups, and that the issues are now resolved. AWS describes the window as between 3:05 AM and 6:10 AM PST (11:05 to 14:10 UTC, 16:35 to 19:40 IST, 06:05 to 09:10 a.m. ET). The most useful thing to do now is to retry any request that failed, as AWS recommends, and to start collecting the times and error messages you will need for any internal review or SLA claim.
Status as of 20:23 IST, 15 November 2026: AWS's latest update, posted at 06:53 PST (20:23 IST), says all services are operating normally and recommends that customers retry any failed requests. AWS has not published a post-incident summary.
What happened
All times below come from the publication times in the AWS Health Dashboard RSS feed (shown in PST by the feed). ET is Eastern Standard Time (UTC-5) on this date; IST is UTC+5:30. AWS did not publish an incident ID in the feed items. Quotes are short excerpts; the feed items are longer.
| Time (PST) | UTC | IST | ET | AWS update |
|---|---|---|---|---|
| 04:38, 15 Nov | 12:38 | 18:08 | 07:38 | "We are investigating reports of Connectivity issues in the US-EAST-1 Region." AWS also said IAM Identity Center sign-in requests and AWS SignUps were impacted. |
| 05:15, 15 Nov | 13:15 | 18:45 | 08:15 | AWS confirmed errors when authenticating with Identity Center or services that rely on it. "For Kiro users, logins from social sign in methods are not impacted at this time." "There are no workarounds for impacted customers." |
| 05:22, 15 Nov | 13:22 | 18:52 | 08:22 | "We are seeing early signs of recovery for authentication via IAM Identity Center and SignUp." |
| 06:23, 15 Nov | 14:23 | 19:53 | 09:23 | AWS said most services had recovered and that the Identity Center authentication errors affecting Kiro, Connect and other services were fully mitigated. It was still investigating a Network Load Balancer (NLB) issue in a single cell in use1-az1: "we recommend creating a new NLB with targets in multiple Availability Zones." AWS said its next update would come by 7:30 AM PST. |
| 06:32, 15 Nov | 14:32 | 20:02 | 09:32 | "We are seeing significant signs of recovery and are continuing to monitor for full recovery." |
| 06:53, 15 Nov | 14:53 | 20:23 | 09:53 | "Service is operating normally: [RESOLVED] Increased Connectivity issues in US-EAST-1". AWS said that between 3:05 AM and 6:10 AM PST customers experienced signup errors, authentication issues and connectivity issues. It said IAM Identity Center authentication was fully mitigated at 5:20 AM, and that a subset of NLB connectivity issues in one cell in use1-az1 was fixed at 6:21 AM. It recommends customers retry any failed requests. |
All items except the last carry the title "Service impact: Increased Connectivity issues in US-EAST-1". Note that AWS's own impact window starts at 3:05 AM PST, earlier than the first feed item at 04:38 PST. The interactive Health Dashboard page is dynamic and could not be loaded, so it may show details that this article does not have.
What AWS has not said, as of the latest update: the cause. This article does not guess at it.
How to check status
- AWS Health Dashboard, Service health: open https://health.aws.amazon.com/health/status. AWS documents that you do not need to sign in or have an AWS account to view it, and that it shows only public events. Choose Open and recent issues to see the event name, the Region, severity such as Impacted or Degraded, a timeline of updates and a list of other affected services. You can show events in your local time zone or UTC.
- Your account health: if you can sign in to an AWS account, the dashboard redirects to AWS Health Dashboard - Your account health, which shows events specific to your account.
- Service history: choose Service history to see all service interruptions of the last 12 months, filterable by service, Region and date.
- RSS and EventBridge: an RSS feed exists, but AWS notes the format is subject to change and recommends Amazon EventBridge for programmatic ingestion of health events.
- Downdetector and social media: these show user reports only, not confirmed impact. Treat any user counts as claims.
What users can do now
- Retry any sign-in or request that failed between roughly 3:05 AM and 6:10 AM PST on 15 November 2026 (16:35 to 19:40 IST), because AWS recommends that customers retry any failed requests.
- If a retry still fails, check the AWS Health Dashboard for a new event before taking action; AWS's resolution notice says services are operating normally, so a continuing failure may be specific to your account.
- Do not reset passwords, remove MFA devices or re-create users to deal with the outage; AWS described a service-side problem, and these changes may leave you locked out later.
- To sign in, open your AWS access portal URL, which looks like
d-xxxxxxxxxx.awsapps.com/startoryour_subdomain.awsapps.com/start, and sign in with your company credentials (AWS documentation on signing in to the access portal). - Treat it as recovered when a normal sign-in works again, in addition to AWS's resolution notice.
What admins should do
- Communicate. Tell users that AWS has marked the US-EAST-1 incident resolved and that failed requests should be retried.
- Check load balancers. AWS said a subset of NLB connectivity issues in one cell in use1-az1 was fixed at 6:21 AM PST. If an NLB of yours still misbehaves, AWS's 06:23 PST guidance for customers who needed immediate resolution was to create a new NLB with targets in multiple Availability Zones; confirm against your own account health first.
- Follow your account health view and subscribe to notifications through Amazon EventBridge, as AWS recommends, so the next time you do not depend on a web page.
- Check your own emergency access. AWS documents an emergency access configuration for the "unlikely event of an IAM Identity Center or AWS Region disruption". Per that page, it works when Identity Center is unavailable but "the IAM data plane and your external identity provider (IdP) are available". The same page warns that you should deploy it before a disruption "because you cannot create the configuration if your access to create the required IAM roles is also disrupted".
- Review jobs that fetch credentials through Identity Center and failed during the window, and rerun them where safe.
- Document the impact for a later review and any SLA claim: first and last failed sign-in times with time zone, the accounts and Region, error messages, affected people and business processes, and AWS case numbers.
For background on how Identity Center fits your accounts, see IAM Identity Center with Entra ID SSO and AWS IAM basics.
SLA credits
The Amazon Compute Service Level Agreement (https://aws.amazon.com/compute/sla/, last updated May 25, 2022 per the page) covers Amazon EC2 and related compute services, not IAM Identity Center, so whether this outage qualifies for any credit depends on the SLA for the specific service you use. No IAM Identity Center or Network Load Balancer SLA was opened, so this article gives no percentages or uptime figures.
What that Compute SLA says about the claim process, as a guide to how AWS handles credits:
- "To receive a Service Credit, you must submit a claim by opening a case in the AWS Support Center."
- The request needs the incident dates and times, the affected Region, resource IDs and supporting logs with sensitive data redacted.
- "Your credit request must be received by us by the end of the second billing cycle after which the incident occurred."
Credits are not automatic. Start collecting evidence now, and read the SLA page for each service you depend on.
Post-incident review
As of 20:23 IST, 15 November 2026, no post-incident summary was found from AWS for this event. AWS publishes event updates on the Health Dashboard; check Service history there and AWS's own announcements for any later write-up. Any statement about the cause should come from AWS, not from forum posts.
If it happens again
Test the emergency access configuration from the AWS documentation before you need it, keep a documented break-glass procedure, and subscribe your operations team to AWS Health events through EventBridge.
What we checked
- Read the AWS Health Dashboard RSS feed (status.aws.amazon.com/rss/all.rss) on 15 November 2026 after the resolution notice (20:23 IST). It contained six US-EAST-1 items, from 04:38 to 06:53 PST, summarized and excerpted above.
- Confirmed the time conversions: 06:53:29 PST is 14:53:29 UTC, which is 20:23 IST and 09:53 a.m. ET; 05:22 PST is 13:22 UTC, 18:52 IST, 08:22 a.m. ET; 06:23 PST is 14:23 UTC, 19:53 IST, 09:23 a.m. ET; 3:05 AM PST is 11:05 UTC, 16:35 IST.
- Cross-checked the resolution notice against the 06:23 PST update: both say the Identity Center authentication errors were fully mitigated and that the NLB issue was confined to one cell in use1-az1.
- Opened status.aws.amazon.com, which redirects to health.aws.amazon.com/health/status; it is a dynamic page that could not be read, so the dashboard's affected-service list is unverified.
- Earlier today, opened AWS documentation on the Health Dashboard, the IAM Identity Center access portal sign-in page and emergency access page, and the Amazon Compute SLA page. The sign-in URL format and the emergency access wording are quoted from those pages.
- Claims only: any Downdetector or social media numbers; none are used here.
- Not tested on a live AWS account; the sign-in errors could not be reproduced, and no post-incident review existed at the time.
Last tested: 2026-11-15
Sources
- AWS Health Dashboard RSS feed: https://status.aws.amazon.com/rss/all.rss
- AWS Health Dashboard, Service health: https://health.aws.amazon.com/health/status
- AWS Health User Guide, AWS Health Dashboard: https://docs.aws.amazon.com/health/latest/ug/aws-health-dashboard-status.html
- IAM Identity Center, signing in to the AWS access portal: https://docs.aws.amazon.com/singlesignon/latest/userguide/howtosignin.html
- IAM Identity Center, emergency access: https://docs.aws.amazon.com/singlesignon/latest/userguide/emergency-access.html
- Amazon Compute Service Level Agreement: https://aws.amazon.com/compute/sla/
This guide was researched and drafted with AI assistance and checked against the vendor documentation listed in its References. Read the maintained version and related guides on EpiFive.
