Hi Khuong, Thank you for the inquiry. This is expected behavior. The best method for you to mitigate this would be to not configure the ELB in Scalr. If the ELB configured in Scalr, then Scalr will manage instance registration and deregistration automatically. If you chose not to configure your ELB in Scalr, then you will be able to (and must) manually manage all registration and deregistration of instances. By the way, welcome to the Scalr Open Source community! We're glad to hear you have been using Scalr for quite some time and are excited to have you join us.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Wednesday, May 17, 2017 at 9:46:41 AM UTC-6, khuong...@zinio.com wrote: > > > Hi Folks, > > We have been using scalr to manage our infra in AWS for long time. > We have a staging env which has an ELB and 2 varnish EC2 instances. > We build a two new varnish EC2 instances using ASG but not managed by > scalr. > > We encountered the problem is Scalr automatically remove the 2 new EC > instances from the ELB. > > My question is how does we avoid this ? > > I would appreciate very much if you can help us on this matter. > > Thanks, > Khuong > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to scalr-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
