1 Answer
- Newest
- Most votes
- Most comments
2
It might be because of the Healthcheck you have configured at the Loadbalancer level.
Relevant content
- Accepted Answerasked a year ago
- asked 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 months ago
It was actually something else. I was using an image on EC2 created for the A1 subnet (for example). In the autoscaling had configured to create the EC2 in any subnet, it happens that when he created for others than the A1 the error occurred. It was just configuring EC2 to always create in the same subnet as the image and it worked.
I would have liked to have created the image without setting the default subnet so that it would use them randomly. When I use the standard AWS VPC it even works, but with my private one I couldn't do that