Infrastructure as Software
summary
Argues that using Pulumi and AWS CDK turns infrastructure into real programs so teams get loops, classes, testing and reuse instead of YAML boilerplate; demo reduces a Kubernetes guestbook from 147 lines to ~20 lines, provisions an EKS cluster end-to-end (VPC, control plane, ASG workers, kubeconfig exported) and deploys Helm charts with drift detection and previews; Pulumi is multi‑cloud and Kubernetes‑first, CDK compiles to CloudFormation and both enable inline Lambdas, unit tests and safer, auditable deployments.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:19What This Talk Is About
- 0:47Infrastructure Provisioning
- 3:54Evolving the paradigm
- 4:28Infrastructure as Software
- 7:00Existing solutions
- 10:30Pulumi comparisons
- 11:53Pulumi Cloud
- 16:39Pulumi Kubernetes Clusters - EKS
- 18:30Pulumi Helm
- 20:39Pulumi Serverless
- 22:01Infrastructure Testing
- 22:52Pulumi Testing
- 23:57Pulumi Findings
- 26:41AWS CDK - Multi Language Support.
- 28:09AWS CDK Testing
- 28:28AWS CDK Serverless
- 30:29AWS CDK EKS - Control Plane
- 31:15AWS CDK EKS Testing
- 31:32AWS CDK - Recap
- 32:11Cultural Readiness
- 33:23Wrap Up
- 34:12References
related talks
39m.NET: Infrastructure as Software
40mStop configuring infrastructure, start coding it!
44mInfrastructure as Code with AWS CDK (the Java version)
52mAWS CDK: The arrival of true Infrastructure as Code
34mPulumi, the Open IaC — the Replacement for Terraform?
29mThe Key to Faster Delivery: Collaborative Platform Strategies
27mProviding a Rich Interface to the Prometheus Operator
25mThe IaC Tooling Face-off for Modern Cloud Native Ops