The challenges of blue/green deployment with AWS Lambda and CloudFormation

I’ve been thinking a lot about how I want serverless code and infrastructure evolution to work

The ever-growing list of Lambda versions doesn’t seem like it belongs in CloudFormation
Step 1. Deployment the first version
Step 2: Weighted alias updated with new version reference
Step 3: Rollout using the weighted alias
Step 4: Update the stack to remove the older Deployment resource
Updated diagram showing usage of Deployment resources

Cloud Robotics Research Scientist at @iRobot