2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
You'll want to attach the Target Group or Classic Load Balancer to the AutoScaling Group: https://docs.aws.amazon.com/autoscaling/ec2/userguide/attach-load-balancer-asg.html
This way any time AutoScaling launches an instance, it will register the instance to the Load Balancer. Similarly, AutoScaling will deregister the instance from the load balancer before it terminates an instance
con risposta 2 anni fa
0
I have added the target group to the ASG however I noticed that when the instance gets terminated the ASG creates 2 instances instead of one in the registered targets. To give you more details on my setup: I have one load balancer and if a path is accessed it uses another instance. How can I only limit one target to be created in registered targets?
con risposta 2 anni fa
Contenuto pertinente
AWS UFFICIALEAggiornata 4 mesi fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
Thank you for your response! I have added the target group to the autoscaling group. I tried to simulate manual AutoScaling however this didn't terminate and create a new instance therefore I'm not sure that everything will work as expected. I would like to set up a cloud watch alert so that if there is no target associated an email or SMS is sent. I have selected this "HTTPCode_Target_5XX_Count" as the metric however I get insufficient data, is there another metric that could help me be aware of this, please?