Keep an instance attached to ELB when autoscale is scaled to

I have a use case to keep selected instances during a zoom event in an ELB application. I know it has a connection timeout with a maximum of 1 hour, but is too short. I have Lifecycle hooks on an instance to send heartbeat, so the instance will not be removed from the ASG, but it will be removed from the ELB after an hour.

Is there a way to keep the instance attached to ELB until the heartbeat stops. Actual use case: I have a video bridging server in the Autoscaling group, so in the scale, in case I don't want users to be disconnected, instead move the instance to maintenance mode (no new calls will be scheduled) and wait until the started calls are zero and finally removed from both ASG and ELB.

+3
amazon-web-services amazon-ec2 autoscaling


source to share


No one has answered this question yet

Check out similar questions:

five
Auto Scaling ECS ​​Cluster to / from Zero Instances
4
The autoscale group never launches any instances
3
Force stops using pending AutoScaling instances: Wait
2
AWS autoscaling launches non-staged instances due to userdata script
2
Kubernetes pod autoscaling not syncing with autoscaling of a group of instances
1
ELB firewall connection errors when canceling ec2 instances
1
AWS Autoscaling Group Health Check Type: ELB or EC2?
0
ec2 instance exited without terminating lifecycle activity
0
How do I end a long running Tomcat task when AWS AutoScaling shuts down an EC2 instance?
0
Does elastic load balancing (ELB) set the number of instances in an AutoScaling group when using CloudWatch policies?



All Articles
Loading...
X
Show
Funny
Dev
Pics