Which strategy for the build and deployment should the developer use to meet these requirements?
Build the code locally, and then upload the code into the source control system. When a release is needed, run AWS CodePipeline to extract the uploaded build and deploy the resources.
Use the AWS Serverless Application Model (AWS SAM) CLI to build and deploy the application from the developer’s local machine with the latest version checked out locally.
Use AWS CodeBuild and AWS CodePipeline to invoke builds and corresponding deployments when configured source controlled branches have pull requests merged into them
Use the Lambda console to upload a .zip file of the application that is created by the AWS Serverless Application Model (AWS SAM) CLI build command.
Explanations:
This approach requires manual intervention to upload the code into the source control system and deploy it via AWS CodePipeline, leading to extra steps.
The AWS SAM CLI is used for local development and testing, not for continuous integration and deployment in a team environment. It lacks automation.
Using AWS CodeBuild and AWS CodePipeline automates the process, triggering builds and deployments on code changes (e.g., pull requests), minimizing manual steps.
Uploading code through the Lambda console is manual and doesn’t scale well for frequent code changes in a team environment. It is not suitable for automation.
I scheme that the answer is:
Use AWS CodeBuild and AWS CodePipeline to invoke builds and corresponding deployments when configured source controlled branches have pull requests merged into them
I classify that the answer is:
Use AWS CodeBuild and AWS CodePipeline to invoke builds and corresponding deployments when configured source controlled branches have pull requests merged into them