1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
as per your case two cases applicable -
-
maybe Its not because of server restart, its basically because of the auto scaling mechanism in which new instances of your basic instance will be created and based on the usage it will delete instance with less usage.
-
if you have checked the logs and found that yes Beanstalk has restarted by itself. you can take screenshot of the log and raise a ticket in aws support asking why it happened.
con risposta 2 anni fa
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks for the answer
Believe it couldn't have been the scaling mechanism, server usage was at just 6%. Is there another reason the scaling engine appears?
Could it have something to do with the free tier exceeding the usage limit? When the usage limit is reached, does it recreate a new server?