Is anyone else getting 503 errors signing in to AWS Identity Center in us-east-1?

November 19, 2026 4 answers
Asked by p.381~quendari

The AWS access portal is returning a 503 in us-east-1, but the health dashboard doesn't show an incident. Is this a wider issue or something specific to our sign-in setup?

Answers

_e61+drimlano.7

Other users have reported the same access portal sign-in error in us-east-1, so it may not be specific to your setup. The health page was updated later, so check it again for any relevant details.

Reply to this answer
q.847~gasketmarble

A 503 at the access portal doesn't necessarily mean every AWS session is broken. Some existing sign-in sessions were reported to keep working, even while new sign-ins failed. Check whether anyone with an existing session can still access what they need.

Reply to this answer
c.735!parcelgizmo

There was also a report of us-east-2 sign-in working while us-east-1 had trouble. That comparison might help narrow down the symptoms, though it doesn't establish that every other region is unaffected.

Reply to this answer
9h!claspvisor_314

If you're still blocked, open an AWS Support ticket with the affected region, approximate time and error details. A separate root sign-in was reported to work, but that doesn't mean the access portal problem is fixed.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions