Building Architectures for Platform Engineering on AWS
summary
Describes how to build a Platform Engineering stack on AWS using patterns like cluster-as-a-service, namespace-as-a-service, and template-as-a-service, and argues tradeoffs between them. Maps a Canary-style stack built from Backstage, Argo CD, Crossplane and Caverno, and gives a worked example integrating Private GitLab, AWS Secrets Manager, KMS/PGP signing, Keycloak for identity and DataDog for observability, with a 5,000-employee / 2,000-tech / 500-apps reference scale; notes awareness of AWS Proton but no personal use.
AI-written summary · about
chapters (10)
- 0:00Platform Engineering intro
- 1:06Platform vs DevOps and SRE
- 3:16Modern platform challenges
- 5:23Why companies need Platform Engineering
- 6:26Platform design patterns
- 8:59Platform design prerequisites
- 11:07Backstack vs Canstack
- 13:34Canstack components
- 14:38AWS services for Platform Engineering
- 15:42Canstack AWS example
related talks
22mStitching the CNCF Stack for Platform Engineers
45mA practical guide to designing your AWS Architecture
40mScaling Startup for Success: Building modern Architectures and Developer Acceleration
12mUnveiling the Future: Navigating Cloud Strategy, Platform Engineering, and Architectural Evolution
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
24mA Cloud Native Foundation For Developer/Application Platforms
45mPlatform Engineering vs DevOps
44mIs Platform Engineering a hype? Let's build a platform together!