How to automatically register Target Groups in Elastic Beanstalk?

Question

I have an application in Elastic Beanstalk that when I changed his ability and configured the health check started giving 503 Service Temporarily Unavailable. After a while I saw that it had some connection with Target Groups.

I went there and added the instance in Target Groups and solved.

However, I ran a third Analytics that does requests and I realized that the ELB went up a new instance and then voided the previous one, or something like that. This way removed the registration of Target Group.

Where can I automate this? By uploading a new instance to add in Target Group? Never gave this problem, will something was undone and now I’m having to add manually but there is a way to be automatic?

Answer 1

I was able to identify the problem that was occurring.

For some reason ended up creating a new Target Group, so ended up getting 2 Target Groups for the same environment.

In the old Target Group, when creating or deleting a new instance, it automatically attached the environment, but in the new Target Group it did not.

In EC2 > Load Balancer > meu-ambiente > Listeners, door 80 was directing to the old Target Group and door 443 was directing to Target Group New.

Solution: I edited and defined both the Port 80 and 443 Systems for the old Target Group that already did everything automatically.