From Monolith to Multi-Account: Pinterest’s AWS Organization Transformation Journey
AWS Cloud Operations Blog
This article details Pinterest's transformation from a single monolithic AWS account to a multi-account architecture, addressing scalability and security challenges at enterprise scale.
- Pinterest faced API throttling, resource limits, and security complexity in single shared account
- Designed new OU structure with Security, Corporate, Sandbox, Services, and Vendor classifications
- Used Moka (Spark on EKS) project as first production multi-account customer to validate approach
- Created new AWS Organization with dedicated management account, migrating all existing accounts
- Built custom account provisioning automation reducing setup time from one month to two weeks
- Implemented centralized networking using VPC sharing and IPAM for efficient resource management
- Adopted AWS managed security services: CloudTrail, Security Hub, Config, IAM Identity Center
- Established reusable architecture standards and baseline security controls for production accounts
Pinterest's multi-account migration demonstrates how large-scale organizations can systematically adopt AWS governance best practices through careful planning, automation, and phased implementation.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
2026
2026
2026
2026
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.