1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
I have reasearched about this and found that when elastic beanstalk is stuck, desired, max and min are set to zero in autoscaling group and then the application is deployed. Then return to previous settings and deploy again and it would then show ok. I am not sure if this can be done or it resolves your problem but you can try. I highly recommend that you reach out to support team here : https://aws.amazon.com/support/
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 mesi fa
- AWS UFFICIALEAggiornata un anno fa
Thanks for your response! I did check the autoscaling policy and set all three settings to zero, but I think the trigger for the policy was not hit ( NetworkOut > 6000000 for more than 5 minutes), so it never added a new instance to the environment. We will have to update the policy for a more accurate trigger in the future.
I checked this morning, and eventually the hanging environment registered a failed update. I initiated a terminate environment command, but it failed because I already manually deleted the RDS instance. Is there a way to force terminate the environment? Or should I delete the CloudFormation stack myself? Will this also terminate the Elastic Beanstalk environment? It's a little hard to glean the answers to these questions from searching through AWS docs.
I have found this link to terminate the environment. It includes force terminate option, just in case you have not already seen it. It is advisable to reach out to support if this doesn't work. https://awscli.amazonaws.com/v2/documentation/api/latest/reference/elasticbeanstalk/terminate-environment.html