Over the past few weeks we’ve been writing about various topics around how to build and maintain a CI/CD pipeline for Serverless Framework applications on AWS.

This post is a compilation of all the topics we’ve covered. We think this should give you all you need to build out your own production-ready CI/CD Serverless pipeline.

Feel free to use this page as a reference. And make sure to bookmark this page and share it with your friends.

Overview

Should I use a hosted or on-premise CI/CD for my Serverless app?

Why a traditional CI/CD service isn’t a good fit for monorepo Serverless apps?

Guides

How to build a CI/CD pipeline for Serverless apps with CircleCI

How to build a CI/CD pipeline for Serverless apps with Travis CI

How to build a CI/CD pipeline for Serverless apps with AWS CodePipeline and CodeBuild

Deployment Workflows

Testing your Serverless app

Git workflow for Serverless apps

How to manage secrets for your Serverless app

Why deploy your Serverless app into multiple AWS accounts?

How to deploy your Serverless app into multiple AWS accounts

Deploying a monorepo Serverless app with interdependent services

How to deploy only the updated services in a monorepo Serverless app

Production Deployments

What is the right way to do rollbacks in Serverless apps?

How to prevent accidentally deleting Serverless resources

Why Serverless deployment artifacts cannot be reused across stages?

Why you should use a manual approval step in a Serverless CI/CD pipeline?

How to generate deployment artifacts in your CI/CD pipeline for Serverless apps

How to handle service dependencies when rolling back a monorepo Serverless app

Reference

CircleCI vs Travis CI vs CodePipeline vs Seed