We have an issue where the ASG will rebalance across AZs while we're in the middle of a deploy. For example, we have four instances...
1 in a, 1 in b, and 2 in c.
If the deploy starts with the instance in a, then the ASG will immediately start trying to rebalance across AZs. This causes an instance to come up with an old version of code since the new version has not yet successfully deployed.
We have an issue where the ASG will rebalance across AZs while we're in the middle of a deploy. For example, we have four instances...
1 in a, 1 in b, and 2 in c.
If the deploy starts with the instance in a, then the ASG will immediately start trying to rebalance across AZs. This causes an instance to come up with an old version of code since the new version has not yet successfully deployed.