How can the developer achieve this goal with the LEAST operational overhead?
Use AWS OpsWorks to perform blue/green deployments.
Use a function alias with different versions.
Maintain deployment packages for older versions in Amazon S3.
Use AWS CodePipeline for deployments and rollbacks.
Explanations:
AWS OpsWorks is a configuration management service for automating infrastructure tasks. It is not designed for Lambda function versioning or rollbacks, and using it for blue/green deployments adds unnecessary overhead for this specific Lambda use case.
AWS Lambda supports versioning, and using a function alias allows you to quickly switch between different versions of the function. This approach is efficient for rolling back to earlier versions with minimal operational overhead.
Storing older deployment packages in Amazon S3 is not a seamless solution for version rollback. While S3 can store the packages, you would need to manually upload and deploy them, which increases operational overhead.
AWS CodePipeline is a powerful tool for automating deployments, but it introduces additional complexity for simple version rollbacks compared to using Lambda function aliases. It is more suited for complex workflows and not the simplest rollback scenario.
I appraise that the answer is:
Use a function alias with different versions.
If memory serves me right, the answer is:
Use a function alias with different versions.