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 not made in the main branch, the pipeline would not be triggered as it monitors only the main branch.
A failure in an earlier stage (such as in CodeBuild) would prevent the pipeline from proceeding to the deployment stage with CodeDeploy.
AWS CodePipeline does not run on EC2 instances directly; it is a managed service and does not rely on EC2 instances in a cluster.
Since the pipeline has been working for months without changes, it is unlikely that the CodeDeploy configuration in the pipeline is suddenly incorrect.
Permissions issues with AWS CodeCommit would have caused issues earlier, and the question indicates the pipeline was previously functioning well.
I design that the answer is:
The change was not made in the main branch of the AWS CodeCommit repository.