Platform engineering
summary
NS runs apps across multiple clouds and creates one AWS account per team per environment, so engineering builds an account vending machine and an account shredding machine using Step Functions, CDK, Lambdas, CloudFormation StackSets and Control Tower to provision networking, IAM and policies. Deploys take 10–15 minutes so a write deploy test loop is slow, and account removal hits AWS’s 10% removal quota, so systems reuse emptied accounts to run a dry-run every 24 hours and alert on failures to meet same‑business‑day SLAs.
AI-written summary · about
chapters (9)
- 0:00Platform engineering intro at NS
- 1:49Landing zone for teams
- 2:37Account provisioning necessity
- 3:20Organizing AWS accounts
- 5:06Account life cycle at NS
- 7:15Account vending machines
- 9:22Reliability with dry runs
- 11:29Reusing accounts to avoid quotas
- 13:34Conclusion & Q&A
related talks
36mBuilding a Secure AWS Self-Service Platform for Regulated Industries
17mGoing Full Silo - Using Serverless to Build for Dev Simplicity
32mCreate a cloud-ready environment
28mStay in Control While Moving Fast
17mBuilding Architectures for Platform Engineering on AWS
41mBuild cloud foundations for growth and resilience
36mPractical Cloud Native: What Works, What Doesn't
30mBuilding Applications in the Cloud: Best Practices