A pipeline must build a container image, push it to a private registry, and deploy to a Kubernetes cluster. The source code lives in GitHub, and the company will not use CodeCommit for its repositories. Which source integration should the pipeline use?
Show answer and explanation
Answer: D
CodePipeline connects to GitHub, GitLab, and Bitbucket through AWS CodeConnections, formerly named CodeStar Connections. A connection authorized once can trigger the pipeline on commits and supply the source artifact for build stages. Because the company is not using CodeCommit, a third-party provider through CodeConnections is the supported path. FTP and manual ZIP uploads are not modern source integrations, and they lose commit-driven triggers.
Why the other options are wrong
- A. FTP is not a supported CodePipeline source provider. Transferring archives this way would require custom code and would miss commit-driven triggers.
- B. Manual S3 uploads remove the commit trigger and the link to repository history. Automated pipelines need a source provider that reacts to pushes.
- C. CodeCommit is excluded by the company's decision, so a design that depends on it cannot be used for these repositories.