Amazon Web Services is updating its sign‑in page to make access simpler while keeping existing authentication methods intact.
The change introduces an email‑first screen that routes users to the appropriate sign‑in path based on the address they provide.
By delaying the choice between root, IAM, or federated login until after the email is entered, AWS reduces confusion for occasional administrators.
Root users and accounts created via the newer sign‑up flow will primarily use the email route, while IAM users still see their familiar credential prompts after selecting the IAM option.
The underlying authentication backend remains unchanged; only the presentation layer has been refreshed, so MFA, password policies, and account‑level controls continue to work as before.
AWS also adds native buttons for external identity providers such as Google, GitHub, Apple, and Amazon.com for accounts that were originally created with those providers.
This federated option is limited to accounts that were initially linked to the provider, preventing retroactive enablement that could lead to privilege escalation.
Customers using AWS IAM Identity Center (formerly AWS SSO) or custom federation solutions will see no disruption; they should continue signing in through their organization’s access portal.
Before the new experience becomes default, a banner invites users to opt‑in, allowing them to test the flow and revert by clearing browser cookies if needed.
The session selection page has received a matching redesign, showing active sessions in a sortable view with account name, role, and timestamp.
From this hub users can launch new sessions, sign out of selected ones, or terminate all active sessions with a single click—a useful feature for shared workstations.
Administrators should update documentation, adjust any UI‑scraping automation, enforce MFA and least‑privilege policies, and communicate the change to end‑users for a smooth transition.