- Newest
- Most votes
- Most comments
They can, but note that this will not utilize connection draining, as they'd be changing DNS to point at a different ELB. When that happens, existing connections to the old load balancer are unaffected until the client re-connects or re-resolves DNS.
Another option is they could attach the new ASG not detach the old ASG, instead having all of the backends in the old ASG fail their health checks. They could then wait the (desired draining time - the configured draining time) and de-register the ASG then. The advantage of this over Route53 is the client's don't have to worry about DNS, you don't have to maintain 2 ELBs, and you can have draining time however long you desire. This works because CLB treats unhealthy backends similarly to de-registered ones, allowing in-flight requests to complete and not sending new requests. Note that TCP listeners a connection to an unhealthy target won't be interrupted by the ELB, and will only fail or close if the client or backend causes it to.
Relevant content
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago