My assumption is that you want more control over when your pipeline does certain things.

Rather than achieving this through stopping the pipeline from getting triggered, I'd recommend using either stage transitions or manual approvals to achieve this control inside the pipeline.

Stage transitions are better when you want to "turn off" a pipeline and have the latest thing run through when you turn it back on.

Manual approvals are better when you want the version to be locked while waiting for approval so you can run tests without worrying that the version will change.

You mentioned in your comment that you wanted to only run your pipeline at certain times, so a way you could do that is to enable and disable the stage transition after source on a schedule.

https://docs.aws.amazon.com/codepipeline/latest/userguide/transitions.html https://docs.aws.amazon.com/codepipeline/latest/userguide/approvals.html

You can disable DetectChanges parameter on your Source action as explained here. Extract with the relevant context:

DetectChanges: Controls automatically starting your pipeline when a new commit is made on the configured repository and branch. If unspecified, the default value is true, and the field does not display by default.

This works on Bitbucket, GitHub, and GitHub Enterprise Server actions. I have a CloudFormation template configured with this option and works. Not sure about the same option on AWS console, because I saw that some configurations are only available from CloudFormation or aws cli. As you can read "this field does not display by default".