Not sure why you got downvoted. The problem is with your deploy system. You can consider each of the clusters to be a service. Thus, a change in Service A (clu

Not sure why you got downvoted. The problem is with your deploy system. You can consider each of the clusters to be a service. Thus, a change in Service A (cluster A), should not trigger a deployment of Service B (cluster B). My pipeline is split in 2: 1. on bitbucket, we run a pipeline that builds "build artefacts", docker images and "packaged" cloudformation templates. Each of these artefacts has a list of triggers, either base docker images or source code. I'm building the relevant docker image or cf package based on the triggers (it's quite a naïve glob() use). 2. On aws side, I have something I call AWS Apps, in short a Stack Name, along with a set of triggers (the above build artefacts). On merge to main, I only deploy the AWS Apps affected by new build artefacts.