Centralized Settings Platform
Owning shared settings infrastructure used by 100+ AWS services and storing 6B+ settings.

The problem
A consistent Console experience depends on shared infrastructure underneath it. AWS service teams needed a common way to store user and service-specific settings, with the performance, security, and availability expected of an AWS platform.
What I owned
I owned the centralised settings platform used by more than 100 AWS services. My scope combined platform ownership with new settings experiences and coordination across Console, service, and Identity teams.
How I approached it
- Owned the shared platform supporting user and service-specific preferences across AWS.
- Initiated person-level settings so preferences could follow the same human across different IAM principals.
- Defined a migration strategy to initialise the new scope from existing preferences, communicate the change, and let users adjust their settings.