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:
This option requires manual steps for uploading .zip files to the AWS Management Console, which increases operational overhead and does not provide an automated or reliable deployment process.
Using AWS SAM allows for defining serverless applications with minimal coding effort. It integrates with CI/CD pipelines, enabling automated deployment of Lambda functions and infrastructure, which enhances reliability and reduces operational overhead.
While this option uses CI/CD for deployment, it still relies on manually creating and uploading .zip files, increasing operational overhead and making the process less efficient compared to using a framework like AWS SAM.
This option involves building and managing container images, which adds complexity. It requires additional steps for container management and storage, making it less suitable for a straightforward serverless application deployment compared to AWS SAM.