-
Hello Ipetrini,
Good day!
Thank you for bringing this to our attention!
In the original setup, the deployment group used a single tag group:
Tag Group 1: {Type=DataProcessing, Name=Microservice1}
This meant an instance was included if it had either of these tags. When a new EC2 instance was launched with Type=DataProcessing but Name=Microservice2, it still met the deployment criteria, which caused Microservice1 to be installed unexpectedly.
To fix this, the one common approach is to split the single tag group into two:
Tag Group 1: {Type=DataProcessing}
Tag Group 2:{Name=Microservice1}
This ensures only instances with both tags are selected, preventing deployments to Microservice2.
Regarding your first concern, you are right that there is no way to explicitly exclude instances with a Team=HR tag in CodeDeploy’s tag-based filtering. The only way to avoid including unintended instances is to refine the tag groups to be more selective.
We appreciate your keen attention to detail and will update this explanation as soon as possible. Thanks again for your valuable feedback!
Regards,
Neil @ tutorials dojo
