Exam AWS Certified DevOps Engineer - Professional DOP-C02 topic 1 question 16 discussion

A: EventBridge rules are not a requirement for CodePipeline to trigger from a CodeCommit repository. CodePipeline directly integrates with CodeCommit without needing EventBridge. B: is a likely cause. The CodePipeline service role needs permissions to access the CodeCommit repository in order to start the pipeline execution when new code is pushed. C:If the developer was able to push code changes to the CodeCommit repository, then their IAM role permissions with respect to CodeCommit are likely fine. This isn't the issue. D:If the pipeline didn't start, CloudWatch Logs could give insights. However, these logs will only exist if the pipeline actually attempted to start but failed. If the pipeline never started, checking logs won't help. Given these options, Option B: is the correct answer.

B would throw out "Permission denied" error immediately, rather than no reaction for 10 minutes.

Good question! I'm used CodePipeline in a particular lab in last year and now I checked the existence of eventbridge rules created by Codepipeline, impressive.

CodePipeline uses Amazon EventBridge (formerly CloudWatch Events) to trigger a pipeline when changes are pushed to a source like CodeCommit. If no EventBridge rule is in place (or it's misconfigured), the pipeline won’t be triggered, even if code was pushed to the correct branch. The rule must match the repository name, branch, and event type (e.g., CodeCommit Repository State Change → referenceUpdated).

Change detection: When you set up a CodePipeline with a CodeCommit source, the default behavior is to use an EventBridge rule to detect changes in the repository, eliminating the need for manual polling mechanisms

The question states that the developer has pushed the change to the repository, which means CodeCommit has no issue, the pipeline doesn't rely on EvertBridge to trigger.

CodePipeline connects to third-party source providers directly using CodeConnections, https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-connections.html, but it should use EventBridge for CodeCommit, https://docs.aws.amazon.com/codepipeline/latest/userguide/triggering.html.

A. Check that an Amazon EventBridge rule has been created for the main branch to trigger the pipeline. This approach directly addresses the most likely cause: a missing or misconfigured EventBridge rule that prevents CodePipeline from starting in response to changes in the CodeCommit repository.

A - EventBridge rule is one of the recommended ways to configure CodePipeline to automatically trigger based on changes in a CodeCommit repository B - if "Permission denied", the error message should prompt immediately, rather than no reaction for 10 minutes for the pipeline. Mean the pipeline not even start Reference: https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-about-starting.html#change-detection-methods https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-simple-codecommit.html

EventBridge rule is one of the recommended ways to configure CodePipeline to automatically trigger based on changes in a CodeCommit repository

For CodePipeline to be triggered by changes in a CodeCommit repository, an EventBridge rule (formerly CloudWatch Events rule) needs to be set up. This rule listens for specific events (like commits to the main branch) and triggers the pipeline accordingly.

It's B.

the answer is A because if codepipeline has no access to codecommit pipeline is triggered and source stage fails with: ``` The service role or action role doesn’t have the permissions required to access the AWS CodeCommit repository named random-repo. Update the IAM role permissions, and then try again ```

B is right.

Just voting to fix the results, because clearly its B, as explained by top 2 comments here.

The first step in troubleshooting this issue should be to check that the CodePipeline service role has the required permissions to access the CodeCommit repository. If the permissions are correct, then you can proceed with other troubleshooting steps, such as checking the CloudWatch Logs for any errors or failures.

Not sure why most people here are even considering A. CodePipeline does not use Amazon EventBridge to trigger pipeline executions based on changes in CodeCommit repositories. Instead, it directly integrates with CodeCommit and monitors repository changes internally.