CI/CD for AWS Lambdas with Serverless Framework and GitLab CI
summary
Presents a concrete CI/CD setup for AWS Lambda using GitLab CI (chosen over Jenkins) and the Serverless Framework (chosen over AWS SAM). Shows a working pipeline that auto-creates and tears down per-feature isolated stacks, wires monitoring/alerts, pulls secrets from a manager, performs warm-up and prunes Lambda versions to keep two, and includes example plugins and GitLab YAML; the setup scales across ~300 repos, ~130 API Gateways and ~600 Lambdas using three CI runners to reduce manual ops, control costs, and avoid cold-start/versioning issues.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:01Serverless tech and AWS Lambda
- 3:25Serverless app challenges
- 6:15Serverless dev approaches
- 7:45CI/CD pipeline
- 12:13CI/CD tool selection
- 14:49Local dev with Serverless
- 16:17Infrastructure deployment
- 24:13GitLab CI benefits
- 26:42Team roles
- 29:38Implementation results
- 31:25Lambda cost monitoring
- 34:47Serverless best practices
- 38:42Common mistakes and fixes
- 40:30Multi-cloud with Serverless
- 41:12Conclusion and Q&A
related talks
25mCI/CD in AWS Cloud
22mDeploying and Managing AWS Lambda With GitLab CI and Terraform
41mCI/CD in the Serverless Era
09mWorking with Serverless Functions and CI/CD
45mAutomating the Minutia using Serverless and Gitlab CI
44mServerless Continuous Delivery with the Serverless Framework
47mRobust CI/CD Pipelines for Serverless Applications
01h 05mBuilding a full CI/CD deployment pipeline