AM

AWS Management Console

Hundreds of services stitched into one inconsistent navigation shell.

The AWS console is less a product than a federation of teams, and you feel every seam. Each service — EC2, S3, IAM, Lambda — was clearly built by a different group, so layouts, table behaviors, and even the meaning of a blue button shift as you move between them. The unifying thread is the universal service search in the top bar, which most people now rely on because the menu structure is unbrowsable. Resource lists are powerful but unforgiving: tagging, filtering, and region scoping all live in different places, and forgetting which region you're in is a rite of passage. IAM's permission editor exposes raw JSON policy because no abstraction survived contact with its complexity. It rewards expertise and punishes everyone else.

Flows

Flows for AWS Management Console are being captured

We haven't taken AWS Management Console apart screen by screen yet. Explore the UX patterns it's known for, or request an audit of your own product.

Request a UX audit

How does your product compare to AWS Management Console?

Get a free UX Snapshot of your page — a quick read on what works and what to fix.

Get a free UX Snapshot →

Teardowns

Teardowns of AWS Management Console are coming

We haven't published a written teardown of AWS Management Console yet. Explore related topics, or request an audit.

Request a UX audit

Free course

WCAG 2.2 Fundamentals: Audit a Screen for Accessibility

6 lessons · ~25 min

Start lesson 1 →