Building a full CI/CD deployment pipeline
summary
Starts from an empty repo and actually builds a working CI/CD pipeline for a serverless app using CloudFormation to create resources, SAM CLI to build/package the Lambda + API Gateway app, and AWS services like CodeCommit and CodeBuild wired into CodePipeline with artifacts in S3 and explicit IAM roles. It runs build/test/package, creates a CloudFormation changeset (dry‑run) and can pause for manual approval, the first end‑to‑end deployment succeeds, and typical pipeline runs take about 10 minutes.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:29Github
- 2:24Demo
- 3:07Application overview
- 3:37Prerequisites
- 7:44Two separate windows
- 8:07Creating a folder
- 8:53Creating an empty pipeline
- 9:07Using the pipeline
- 12:36Testing the pipeline
- 14:50Confirmation
- 16:21Confirmation Template
- 16:56Name Collision
- 18:44Why did it take so long
- 19:01Adding an S3 bucket
- 19:35Creating a separate S3 bucket
- 21:12Why I hate naming buckets
- 25:02Creating a pipeline role
- 29:57Creating a code build project
- 37:52Pipeline role
- 38:52Pipeline roles
- 40:34Pipeline example
- 42:17Commenting out code
- 44:22Run order
- 44:58Point of test
- 50:20Console Recorder
related talks
25mCI/CD in AWS Cloud
47mRobust CI/CD Pipelines for Serverless Applications
41mCI/CD in the Serverless Era
30mContinuous Integration and Delivery for serverless apps
44mCI/CD for AWS Lambdas with Serverless Framework and GitLab CI
01h 18mBuilding applications with Serverless Framework ...
29mServerless from scratch with CI/CD on AWS: it’s a lot easier than you think (and mostly free).
50mStreamline your Cloud Native Application Deployment using AWS SAM