AWS Lambda, CodeBuild & CloudFormation - Storing Source Code Locations for Build

Supported Locations for Storing Source Code for AWS Serverless Applications

Prev Question Next Question

Question

The deployment team is working on a project for a new serverless application using AWS Lambda, CodeBuild & AWS CloudFormation.

Source code will be accessed by users working on this project from various on-premise locations.

Which of the following are supported locations for storing source code used for build? (Select Three)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

Correct Answer - B, D, E.

AWS CodeBuild supports building a build from a source code located at the following locations.

AWS CodeCommit.

Amazon S3

GitHub.

Bitbucket.

Option A & C are incorrect as EC2 instance & On-Premise local machines are not valid locations that can store source code for creating a build with AWS CodeBuild.

For more information on Source Code location for AWS CodeBuild refer to the following URL-

https://docs.aws.amazon.com/codebuild/latest/userguide/planning.html

Sure, I'd be happy to help!

AWS Lambda, CodeBuild, and CloudFormation are all part of the AWS serverless ecosystem and are designed to work together to enable rapid and efficient development and deployment of serverless applications. As part of this process, source code needs to be stored somewhere where it can be accessed by the development team.

The options for storing source code used for build are as follows:

A. EC2 Instance: This option is not recommended for storing source code used for build as EC2 instances are not typically used for this purpose. EC2 instances are typically used for running applications and other compute-intensive workloads.

B. Amazon S3 Bucket: This is a recommended option for storing source code used for build. S3 buckets are highly scalable, durable, and secure. They are also highly available, meaning that developers can access the source code from anywhere with an internet connection.

C. On-Premise Local machine: This is another option for storing source code used for build. However, it is not recommended because it can lead to issues with version control and synchronization. In addition, it can be difficult to access the source code from different locations.

D. AWS CodeCommit: This is another recommended option for storing source code used for build. CodeCommit is a fully-managed source control service that is highly secure and scalable. It is also integrated with other AWS services, such as CodeBuild and CloudFormation.

E. Bitbucket: This is an option for storing source code used for build, but it is not an AWS service. Bitbucket is a web-based hosting service that is owned by Atlassian. While it is possible to integrate Bitbucket with AWS services such as CodeBuild and CloudFormation, it may not provide the same level of integration and security as AWS CodeCommit.

In summary, the recommended options for storing source code used for build with AWS Lambda, CodeBuild, and CloudFormation are Amazon S3 buckets and AWS CodeCommit. On-premise local machines and Bitbucket are also options, but they may not provide the same level of integration and security as the AWS services. EC2 instances are not typically used for this purpose.