The latest articles on DEV Community by deborah-Cat (@deborahcat). https://dev.to/deborahcat https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F938078%2F0b988fcb-72f8-4a0c-a1ce-b9e16426cbfb.png https://dev.to/deborahcat en deborah-Cat Thu, 03 Nov 2022 08:03:06 +0000 https://dev.to/deborahcat/need-help-issue-with-auto-scaling-for-application-load-balancer-with-2-different-instances-for-target-groups-gp0 https://dev.to/deborahcat/need-help-issue-with-auto-scaling-for-application-load-balancer-with-2-different-instances-for-target-groups-gp0 <p>What is your question/issue (provide as much detail as possible)?</p> <p>Hi All, I currently have an Application Load Balancer that has two rules :</p> <p>If the request is coming from a specific path Example: /test/, use a target group that points to an instance ( Let's say instance b ). For any other request use this target group ( another instance a ) In the autoscaling settings I have added these two target groups so that if autoscaling occurs and terminates the instances, they will be re-registered. This works correctly, however, I noticed that when termination happens the target group registers instance a where only instance b needs to be registered.</p> <p>I do have 2 ASGs, one for the instance a and one for another instance b. However, I mostly use the main site Load balancer as the rules are located there ( if the path of /test/* it uses the instance b ( target group ). The reason this was set like this is that the instance b is accessed by the main site domain. ( For example <a href="http://www.example.com/test">www.example.com/test</a> ) The desired count is set to 1.<br> Since I'm using the ALB of the main site only when the ASG terminates the instance, a new target is registered for the main site in the target group of the instance b. My issue is that this target group should only register one instance and not 2 ( instance a ( main site ) and instance b )</p> <p>Would really appreciate some guidance, haven't received much from Re:post :(</p> <p>What technologies are you using?</p> <p>AWS, AutoScaling, EC2, ElasticBeanstalk</p> <p>What were you expecting to happen?</p> <p>When Autoscaling terminates the instance, the target group that has instance b registers, initiates another instance and places the same instance b and not another instance a. </p> <p>What is actually happening?</p> <p>When Autoscaling terminates the instance, the target group is adding another instance a and therefore the site breaks as the incorrect server is being shown.</p> <p>What have you already tried/thought about?</p> <p>Maybe having one autoscaling group for two different instances, however didn't manage. But there is still the issue of cannot control which instance is added to the target group when its terminated.</p> help aws ec2