0

After CodeDeploy clones AutoScalingGroup, it leaves LoadBalancer field empty. This leads to following problem: when instance webserver dies, ELB does not understand instance is "down", this instance is not replaced automatically. However, if i set LoadBalancer manually, it will work fine afterwards.

I watched how new ASG is cloned. There is possibility to suspend some processes while instance is booting. So as i understand, CodeDeploy suspends all actions related to ELB, because it uses his own automatic scripts to un-attach old instances and attach new ones to ELB.

fresh ASG

I dont use any custom attach or un-attach scripts myself.

Otherwise deployment runs ok, and new instances are created correctly.

sirandy
  • 1,834
  • 5
  • 27
  • 32
yuriy_shtybel
  • 1
  • What does the deployment configuration looks like? Is it in place or a blue green deployment? – strongjz Jun 08 '17 at 20:03
  • blue-green deployment... – yuriy_shtybel Jun 08 '17 at 21:32
  • Whats the configuration in the deployment group? "Instances in the original environment are deregistered and handled according to your specification in the deployment group, either terminated or kept running." http://docs.aws.amazon.com/codedeploy/latest/userguide/welcome.html#welcome-deployment-overview-blue-green – strongjz Jun 12 '17 at 01:38

1 Answers1

0

I spoke with the team and apparently what's going on is that CodeDeploy now manages the load balancer for you. That is very confusing to customers to not see the ELB associated with that AutoScalingGroup. This allows CodeDeploy to control and make sure that the deployment finishes before binding the to the load balancer.

-Asaf

Asaf Erlich
  • 21
  • 3