Building a Secure AWS Self-Service Platform for Regulated Industries
summary
Shows a concrete IDP that vends governed AWS accounts and environments using ServiceNow, GitLab, Terraform, Control Tower, Service Catalog, Backstage and Argo CD, with account creation taking ~7.5 minutes and full infra plus app deployment ~25 minutes. Security uses a deployment IAM user, a StackSet-injected CICD role with a tight trust policy, and TF modules for VPC/EKS/RDS; costs are surfaced in choices. Implements two flows: ServiceNow → GitLab → Terraform for accounts and Backstage scaffolder generating TF vars for self‑service infra, and it works end‑to‑end.
AI-written summary · about
chapters (10)
- 0:00Introduction to platform engineering
- 1:45Why build an internal platform
- 4:51Key benefits of platform engineering
- 7:19Defining internal developer platforms
- 11:13Creologic’s platform journey
- 20:43AWS architecture for Creologic
- 25:14Demo of account provisioning
- 27:39Demo of infrastructure provisioning
- 32:20Best practices for platform teams
- 34:47Key takeaways and conclusion
related talks
55mBest practices
55mSelf-service infrastructure is no longer a dream
41mBuild cloud foundations for growth and resilience
44mPlatform Engineering in action
14mPlatform engineering
41mAWS Cloud Automation Platform with Terraform and Jenkin
32mAgile governance on AWS GovCloud (US)
18mTerraforming AWS Control Tower
