An IT consulting company starts to use CodePipeline to help manage its development lifecycle since AWS CodePipeline is a great DevOps service. They hope that starting from CodeCommit, the pipeline is able to build the code, test the artifact and deploy the build automatically. They heard that CodePipeline is also very convenient to work together with Jenkins so they decided to use Jenkins as a build provider. Another reason is that they already have very strong experiences on Jenkins for their on-premise applications. Which of the following options is correct on how to use the CodePipeline together with Jenkins?

Answer options:

A.Setup CodePipeline in one region and setup CodeCommit and Amazon EC2 instance key pair in another region. This is to address some safety concerns. Then create a new CodePipeline with 4 stages. In the build stage, choose “Add Jenkins” and configure correct “Provider name” and “Server URL”.
B.Make sure that all of the AWS resources for this procedure are created in the same AWS Region where you create your pipeline. Then create a new CodePipeline with 4 mandatory stages which are “Source Stage”, “Jenkins Stage”, “Test Stage” and “Deploy Stage”.
C.Launch an Amazon EC2 instance to host the Jenkins server and using a Secret Access Key/Access Key ID to grant the instance the required permissions for interacting with AWS CodePipeline. For the new CodePipeline configuration, make sure that Jenkins is selected as the build server in the build stage. The “Server URL” should match that in the Jenkins server however the “Provider name” can be anything.
D.Launch an Amazon EC2 instance to host the Jenkins server and use an IAM role to grant the instance the required permissions for interacting with AWS CodePipeline. Then create a new CodePipeline. In the build stage, choose “Add Jenkins” and configure correct “Provider name” and “Server URL”.

Correct Answer –D
Option D is Correct:
At the moment, CodeBuild, Jenkins and Solano CI can be used as a build provider in the CodePipeline. During the setup of CodePipeline, the user needs to configure the build provider at the “Build Stage” and select Jenkins as below:
After “Add Jenkins” is selected, in Provider name, type the name of the action you provided in the AWS CodePipeline Plugin for Jenkins (for exampleMyJenkinsProviderName). This name must exactly match the name in the AWS CodePipeline Plugin for Jenkins. In Server URL, type the URL of the Amazon EC2 instance where Jenkins is installed. In Project name, type the name of the project you created in Jenkins, such as MyDemoProject, and then choose Next.
About the details on how to setup CodePipeline with Jenkins, refer to https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-four-stage-pipeline.html
Option A is incorrect: because all of the AWS resources for the CodePipeline should be in
the same AWS Region where the CodePipeline is created. For example, if you create your pipeline in the US East (Ohio) Region, your Amazon S3 bucket or AWS CodeCommit repository, AWS CodeDeploy resources, and Amazon EC2 instance key pair must also be in the US East (Ohio) Region. Also, refer to
https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-four-stage-pipeline.html
Option B is incorrect: because the stages of “Jenkins Stage” and “Test Stage” are incorrect. Also the stages are not mandatory and can be optionally skipped. The stages should be “Source Stage”, “Build Stage” and “Deploy Stage”.
Option C is incorrect: because it should not use Secret Access Key/Access Key ID for the Jenkins EC2 instance. The IAM should be used instead. Besides, both “Provider name” and “Server URL” should match those in the Jenkins server.