Release Branches - Serverless Architectures with AWS Lambda

Release Branches

We recommend that you create a repository or project branching strategy that enables you to correlate Lambda function deployments with incremental commits on a release branch. If you don’t have a way to confidently correlate source code changes within your repository and the changes that have been deployed to a live Lambda function, an operational investigation will always begin with trying to identify which version of your code base is the one currently deployed. You should build a CI/CD pipeline (more recommendations for this later) that allows you to correlate Lambda code package creation and deployment times with the code changes that have occurred with your release branch for that Lambda function.