Skip to content
Adila SadovicSenior Product Designer
WorkCloud infrastructure & operations

AWS Quick Setup

Hiding cloud complexity behind user intent

Role
UX Designer
Timeframe
Oct 2020 — Feb 2024
Scope
Console experience, information architecture, terminology, flows

Mandate

Identified that the problem was assembly, not capability, and designed the outcome-first setup model AWS Systems Manager adopted as a platform.

01Problem

The problem wasn't a lack of capability

AWS already had every underlying service customers needed.

The problem was assembling them. A DevOps engineer configuring one operational capability could touch services, accounts, Regions, permissions, resources and organizational units — each individually correct while the end-to-end task stayed difficult.

Available already

  • Services
  • Permissions
  • Accounts & Regions
no unified path

Not yet assembled

  • One workflow
  • Recommended defaults
  • Deployment across scope
02What I changed

Shift from configuration to intent

Before

Configuration started with the system: which service, resource, policy, Region, account.

→

After

Configuration starts with the customer's outcome — the system assembles the rest.

That model runs on one repeatable flow, reused by every configuration in the library:

  1. 01

    Desired outcome

  2. 02

    Recommended configuration

  3. 03

    Scope

  4. 04

    Review

  5. 05

    Deploy

Define once, deploy across accounts: recommended configurations in the management account become governed actions across target environments.Click to enlarge

Decision 01

Start with a library of outcomes

Exposing the underlying services and letting customers compose their own configuration preserved maximum flexibility, and most of the original complexity with it. Quick Setup instead introduced a library of recommended configurations built around common operational needs, so customers chose the capability they wanted rather than first identifying every service needed to create it.

The entry point changed from configuring AWS services to setting up an operational capability.

Decision 02

Separate what from where

Once a customer chose what to configure, the next question was scope — and cloud infrastructure doesn't live in one place. A configuration might apply to one resource, one account, selected accounts and Regions, or an entire organization through AWS Organizations.

The same interaction could represent a single-resource change or an organization-wide one.

AWS Systems Manager Quick Setup library screen listing configuration types including Host Management, Config Recording, Conformance Packs, Change Manager, DevOps Guru and Distributor, each with a status and a Create action.
What a configuration provisions and what it enables, decided before where it deploys.

Decision 03

Recommended defaults first, control second

Infrastructure interfaces often treat flexibility as the same thing as exposing options. Most customers shouldn't need to make every possible decision, so Quick Setup used recommended defaults based on AWS guidance while still allowing deeper customization when the defaults didn't fit.

Recommended path first. Advanced control when needed.

Decision 04

Show the consequence before deployment

If the system does work on the customer's behalf, the customer needs to understand what will happen before committing to it. Selecting a configuration led to a preview of the actions and scope before deployment — what would be created, and where it would run.

The system could hide implementation complexity without becoming opaque.

Quick Setup patch policy form: patch operation set to scan and install, recommended default scanning schedule, custom install schedule with a CRON expression, and options to wait for the first CRON interval and to reboot if needed.
Recommended defaults sit beside custom schedules before anything deploys.
03Beyond the solution

From a setup wizard to a setup platform

01

I identified the deeper problem

The problem wasn't AWS lacking a service — it was that no experience assembled existing services around what an operator was actually trying to do. Naming that reframed Quick Setup from one more console feature into a platform-level fix.

02

The model crossed team boundaries

The configuration library wasn't a fixed collection owned by one team. It was designed so other AWS teams could publish their own configurations while relying on the same setup model — a repeatable grammar other teams didn't need to reinvent.

03

The model had to outlast the first release

The same choose → configure → scope → review → deploy model now spans capabilities well beyond the original patch-management use case, including cross-account experiences spanning observability, cost, compliance and security.

04After

What Quick Setup became

Configuration library

Capabilities presented as configurations an operator can find, compare and provision.

Systems Manager configuration library screen with a search field, popular labels filter and cards for Host Management, Application Management, Resource Management, Agent installation, Machine learning operational monitoring and Compliance Management.
The configuration library: capabilities presented as configurations an operator can find, compare and provision.

Recommended defaults, in the console

Recommended defaults sit beside custom control, so an operator can accept AWS guidance or express an exact policy.

Quick Setup patch policy form: patch operation set to scan and install, recommended default scanning schedule, custom install schedule with a CRON expression, and options to wait for the first CRON interval and to reboot if needed.
Scanning and installation: recommended defaults sit beside custom schedules, so an operator can accept a baseline or express an exact CRON window.
Patch baseline selection listing every supported operating system with a baseline dropdown and baseline ID, three rows highlighted where custom baselines were selected.
Baseline selection across every supported operating system, defaults visible next to an organisation's custom choices.
05Evidence

Program-level impact

64%

Cross-feature adoption

Publicly documented Management Tools program metric — not a causal claim about Quick Setup alone.

Progression

FeaturePlatform

Other AWS teams now publish their own configurations using the same setup model.

20% faster

Reduction in time to first cross-feature adoption, program-wide.

50% MoM growth

Growth in cross-account deployment, program-wide.