Infrastructure as Code on AWS: Deep Dive
summary
Hands-on checklist for CloudFormation and CDK: use cfn-lint and cfn-nag in the editor, run taskcat to deploy templates to multiple regions and get HTML reports, and enforce a pipeline that lints, deploys tests, then promotes to staging and prod. Avoid hard‑coding secrets—use Parameters, Mappings, SSM Parameter Store or Secrets Manager. Use CloudFormation Resource Import and drift detection to adopt existing resources. CDK compiles to CloudFormation, offers constructs/patterns (one line can generate ~817 lines CFN), and supports Jest snapshot and fine‑grained tests.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:13Take it through a pipeline
- 4:52Workflow
- 8:39Best practices start in the code editor
- 12:07Lint twice, deploy once!
- 19:08Best practices (2/3)
- 27:10Patterns
- 30:02Not matching a snapshot
related talks
44mDeep Dive: Infrastructure as Code on AWS
24mInfrastructure as Code on AWS
36mStop configuring infrastructure, start coding it!
42mAWS Cloud Development Kit: Boost your Infrastructure
30mDeveloper guide to infrastructure as code on AWS
52mAWS CDK: The arrival of true Infrastructure as Code
05mLightning Talk: AWS CDK infrastructure as Code
30mStop configuring infrastructure, start coding it!