Stop configuring infrastructure, start coding it!
summary
Argument: replace hand-editing JSON/YAML with real code using the open-source AWS Cloud Development Kit (CDK). CDK compiles TypeScript/Python/Java/C#/JS/Go into CloudFormation, so provisioning, state, rollbacks stay with CloudFormation while developers get IDE tooling, loops, abstractions and reusable constructs. Examples shown: 300 lines of YAML vs ~30 lines of TypeScript, one-line VPC that creates subnets/routes/etc, four-line ECS stack that wires ALB, tasks, IAM, and community counts 1,600+ Construct Libraries. Continuous delivery via pipelines and per-account deployment is supported.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 6:41What is AWS CDK?
- 12:21Understanding CDK constructs
- 21:29CDK in CI/CD pipelines
- 27:04Why code infrastructure instead
- 33:20Q&A session
related talks
41mInfrastructure as Code on AWS: Deep Dive
35mStop being a YAML engineer, be a software engr. with CDK8s
19mCloud infrastructure with AWS Cloud Development Kit
52mAWS CDK: The arrival of true Infrastructure as Code
34mInfrastructure as Software
44mInfrastructure as Code with AWS CDK (the Java version)
30mDeveloper guide to infrastructure as code on AWS
23mCI/CD at Scale: Best practices with AWS DevOps Services