1 Answer
- Newest
- Most votes
- Most comments
0
Well, if anyone had this very same problem... well, yes. It was because it was never healthy. I deployed a WebSockets only server, so it was not handling any http requests over '/'. So elastic beanstalk would consider it dead because it was failing the health check. Once I created an end point, elastic beanstalk could request and get its 200 status code, I managed to upgrade my instance type.
answered 5 years ago
Relevant content
- asked 9 months ago
- asked 6 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 10 months ago