<strong>A team of about 30 developers is working on a photo sharing project. Most of developers are using Github. One developer (Jeffery) has just used CodeCommit for a feature and found that it is very convenient to use. Moreover, the whole project is almost fully developed and integrated under AWS environment. Jeffery just demoed his experience to the team and they agreed to migrate all their existing developments into CodeCommit as well. Some other developers need to work on Jeffery’s CodeCommit code repository too. How should the team migrate to ensure CodeCommit is used properly? Select 2.</strong>

Answer options:

A.Create new CodeCommit Repo when required. Git Clone the Repo in local PCs and the use git push to the new CodeCommit Repo url such as “http://git?-codecommit.us-east-2.amazonaws.com/v1/repos/MyRepository”.? After that, view
files in AWS CodeCommit to see if the git push is successful.
B.Set up new CodeCommit Repo using AWS CLI. Find the repo url which may be a HTTPS or SSH one. Use git push to upload the repo from local to CodeCommit server. After that, inspect if the files show properly in CodeCommit.
C.In order to work on existing CodeCommit Repo for other developers, create an IAM group with a suitable CodeCommit policy. Add users to that group. Then all developers are able to git clone the CodeCommit Repo and start working on their own branches.
D.To work on existing CodeCommit Repo, create an IAM user for each developer, add a CodeCommit Read policy to each user. After that, all developers are able to git clone the CodeCommit Repo and start working on their branches.
E.Make sure that all users have full admin access so that they do not need to worry about the access of CodeCommit. Then they are able to git clone or push any new or existing CodeCommit Repo.

OptionB & C are Correct:
You can migrate an existing Git repository to an AWS CodeCommit repository. This process includes:
Complete the initial setup required for AWS CodeCommit.
Create an AWS CodeCommit repository.
Clone the repository and push it to AWS CodeCommit.
View files in the AWS CodeCommit repository.
Share the AWS CodeCommit repository with your team. Refer to the below link for details: https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-migrate-repository-existin g.html#how-to-migrate-existing-share
Option A is incorrect because the CodeCommit Repo url should be a HTTPS or SSH. HTTP is incorrect.
Option D is incorrect: because the team contains 30 users so it is not proper to assign an IAM policy for each IAM user. Option C is better than Option
D. This is also stated in https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-migrate-repository-existing.html#how-to-migrate-existing-share
Option E is incorrect because full admin access is improper as they only need the CodeCommit relevant access. This option is insecure and not a best practice.