What are the possible causes?
(Choose two.)
The change was not made in the main branch of the AWS CodeCommit repository.
One of the earlier stages in the pipeline failed and the pipeline has terminated.
One of the Amazon EC2 instances in the company’s AWS CodePipeline cluster is inactive.
The AWS CodePipeline is incorrectly configured and is not invoking AWS CodeDeploy.
AWS CodePipeline does not have permissions to access AWS CodeCommit.
Explanations:
If the change was made in a branch other than the main branch, it would not trigger the AWS CodePipeline, as it is specifically configured to react to changes in the main branch of the AWS CodeCommit repository.
If any stage in the pipeline fails, the pipeline will terminate and not proceed to the deployment stage. Therefore, if there was an issue in the earlier stages (like build or test), it would prevent CodeDeploy from executing.
The state of individual Amazon EC2 instances in the CodeDeploy fleet does not affect whether the CodePipeline triggers a deployment. CodeDeploy can handle inactive instances by skipping them during the deployment process.
If the pipeline were incorrectly configured, it would likely have failed to invoke AWS CodeDeploy from the start, not just during the latest change. If the pipeline was successfully triggering before, it’s unlikely that a sudden misconfiguration would only manifest now without other symptoms.
AWS CodePipeline does not require explicit permissions to access AWS CodeCommit if the pipeline has been set up correctly and has been functioning previously. If there were permission issues, the pipeline would not have been able to access the repository at all, leading to failures on every change, not just the recent one.
As I recall, the answer is:
The change was not made in the main branch of the AWS CodeCommit repository.
If I’m correct, the answer is:
The change was not made in the main branch of the AWS CodeCommit repository.