Lessons learned from building a cloud-native platform
summary
Lessons show a cloud native platform built with Terraform and Kubernetes uses multiaccount separation to reduce breach blast radius and meet compliance, and fixes surprise limits like VPC IP exhaustion and overlapping on‑prem address space. The platform enforces encryption at rest and in transit, adopts GitOps via GitHub patterns and reusable Helm charts and Terraform modules, and relies on four observability pillars metrics logs traces alerting. Cost savings come from using spot or preemptible instances when occasional unavailability is acceptable.
AI-written summary · about
related talks
42mLessons Learned as a DevOps Consultant
22mLessons Learned from Scaling Infrastructure as Code
24mHow to survive Cloud – An Ops perspective
24mSelf-Service Multi-Cloud K8s Platform at a Regulated Financial Enterprise
37mBuilding a Managed Platform While Maintaining a Good Developer Experience
15mPaaS isn’t enough: your internal platform in Multi Cloud
40mLessons Learned Building Developer Platforms
39mPerils of the cloud