A team uses CodeCommit for source control and CodePipeline for deployments. They configured the pipeline to trigger on changes to the remote main branch, but after a developer pushed changes the pipeline did not start even after 10 minutes. What should be checked to troubleshoot this trigger issue?

The correct answer is to verify the Amazon EventBridge rule. For CodePipeline to automatically trigger on CodeCommit changes, an EventBridge rule must be configured to detect pushes to the specified branch (in this case, 'main') and initiate the pipeline. If this rule is missing or misconfigured, the pipeline will not start. The other options are less likely to be the primary cause of a trigger issue: If the CodePipeline service role lacked CodeCommit access, the pipeline would likely fail during the source stage, not fail to trigger at all. If the developer's IAM role lacked push permissions, they wouldn't have been able to push changes to the repository in the first place. CloudWatch Logs might show pipeline execution failures, but if the pipeline isn't triggering, there won't be any execution logs to check for CodeCommit errors related to the start.