Reviewable infrastructure indeed
The title is accurate. Everything in this course is about making infrastructure changes safe to approve.
Browse
Define AWS infrastructure in TypeScript with CDK v2, test it with assertions, check it with cdk-nag and deploy it safely through a pipeline
Created by Mateo Silva
The AWS Cloud Development Kit lets you define infrastructure in a real programming language and deploy it through CloudFormation. That brings loops, types, functions and package management to infrastructure. It also brings the risk of clever code nobody can review. This course teaches CDK with a focus on infrastructure that a teammate can read, test and approve.
A small but complete service: a VPC, a containerised API on ECS Fargate behind a load balancer, a PostgreSQL database on RDS, a queue with a worker, alarms and dashboards. We grow it from one stack to several, add tests and policy checks, and finish with a self mutating pipeline that deploys to two environments.
You should know basic TypeScript and have used AWS before. We use CDK v2 with the aws-cdk-lib package, Node.js LTS and the AWS CLI. Everything is deployed into your own account, and we tear down every stack at the end.
Builds serverless and Kubernetes platforms on AWS. Teaches Lambda, CDK and Helm with real projects
I am a platform engineer who moves between two worlds: serverless applications on AWS Lambda and container platforms on Kubernetes. Teams usually need both, and I teach the trade offs honestly.
Each of my courses is built around one project that grows from a single file to something you could hand to a team: an HTTP API, a CDK app with tests, a Helm chart with sane defaults. I care about the parts tutorials skip, such as permissions, configuration per environment, rollbacks and cost.
I write infrastructure in TypeScript and YAML most days and I will show you the mistakes I made so you can skip them.
The title is accurate. Everything in this course is about making infrastructure changes safe to approve.
Reading diffs in three passes is now how our whole team reviews infrastructure pull requests.
I finally understand when to use L1, L2 and L3 and what an escape hatch really does.
Assertions plus the logical id test caught a database replacement in our project before it reached production.
We now fail builds on new nag findings. Clear guidance on writing suppression reasons.
Very good course. Most examples use ECS, which suited me, but Lambda users may want more.
Comparing CDK Pipelines with GitHub Actions helped us choose. The cross stack reference trap lesson saved me a headache.
Content is accurate, but my TypeScript was rusty and some lessons felt fast.