- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
It sounds like the issue you are experiencing is due to the platform update process in Elastic Beanstalk creating new instances and then removing the old instances from the target group.
To avoid this problem, you can create a custom target group for your Elastic Beanstalk instances that will not be impacted by platform updates. You can do this by following these steps:
Create a new target group in the EC2 console.
Configure the new target group to include the port(s) that your Elastic Beanstalk instances are listening on.
Update your Elastic Beanstalk environment to use the new target group instead of the default target group.
Add the new target group to your shared load balancer.
By creating a custom target group, you can ensure that your Elastic Beanstalk instances are always included in the target group, even after platform updates. When a platform update creates new instances, they will automatically be added to the custom target group, while the old instances will remain in the group.
Note that when you create a custom target group, you will need to update your Elastic Beanstalk environment to use it instead of the default target group. This can be done using the Elastic Beanstalk console or the AWS CLI.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Thanks, that seems to be exactly what I need here!
I didn't know I could change a Beanstalk target group like this. I'll take care of it as soon as I have some time.