How AWS Built Its Control Plane for 200 Services

Episode notes

Amazon Web Services runs over 200 services, each with its own control plane. In this episode, Lucas and Luna break down how AWS's internal architecture team designed a unified control plane framework that handles millions of API requests per second across regions. They explore the concept of 'control plane as a platform' - a set of reusable primitives for authorization, rate limiting, and state management that lets service teams focus on business logic. Lucas walks through the key design decisions: separating data plane from control plane at the infrastructure level, using eventual consistency for global state, and the 'cell-based architecture' that isolates failures. Luna asks how this affects developers building on AWS today and whether the pattern is reproducible outside of hyperscalers. A specific look at one of the most complex distributed systems ever built, and what it teaches us about scaling engineering orgs.

• How Airbnb Rebuilt Search for 8 Million Listings62 / 100
• How GitLab Built a Single Codebase for One Million CI Pipelines65 / 100
• How Slack Rebuilt Its Search Index for 10 Million Daily Queries57 / 100
• How Notion Rebuilt Its Sync Engine for Offline-First
• How Notion Rebuilt Its Block Engine for Hybrid Local-Sync