Which method will meet these requirements with the LEAST operational overhead?
Build the application by using shell scripts to create .zip files for each Lambda function. Manually upload the .zip files to the AWS Management Console.
Build the application by using the AWS Serverless Application Model (AWS SAM). Use a continuous integration and continuous delivery (CI/CD) pipeline and the SAM CLI to deploy the Lambda functions.
Build the application by using shell scripts to create .zip files for each Lambda function. Upload the .zip files. Deploy the .zip files as Lambda functions by using the AWS CLI in a continuous integration and continuous delivery (CI/CD) pipeline.
Build a container for each Lambda function. Store the container images in AWS CodeArtifact. Deploy the containers as Lambda functions by using the AWS CLI in a continuous integration and continuous delivery (CI/CD) pipeline.
Explanations:
Manually creating .zip files and uploading them to the AWS Management Console is a manual and error-prone process, with high operational overhead and little automation.
AWS SAM simplifies the deployment of serverless applications with minimal coding effort. It integrates well with CI/CD pipelines and provides a reliable, automated deployment process.
While the CI/CD pipeline helps automate the process, using shell scripts and .zip files introduces unnecessary complexity, and lacks the streamlined infrastructure management provided by SAM.
Building containers for Lambda functions and using AWS CodeArtifact adds complexity without providing significant benefits in terms of reduced operational overhead for serverless applications. SAM is a simpler and more efficient solution.
If memory serves me right, the answer is:
Build the application by using the AWS Serverless Application Model (AWS SAM). Use a continuous integration and continuous delivery (CI/CD) pipeline and the SAM CLI to deploy the Lambda functions.