After eb deploy the environment gets stuck in Health: 'Severe'.
It show the following warning in recent events:
Environment health has transitioned from Info to Severe. ELB processes are not healthy on all instances. Application update in progress on 1 instance. 0 out of 1 instance completed (running for 3 minutes). None of the instances are sending data. ELB health is failing or not available for all instances.
I'm not able to ssh into the instance: connection reset by peer. (I'm normally able to ssh into the instance without any issues).
The request logs function doesn't work because:
An error occurred requesting logs: Environment named portal-api-staging is in an invalid state for this operation. Must be Ready.
Cloudwatch logs only contain the same message from 'recent events'.
How do I figure out what why the deployment fails?
AWS documentation says I should check the logs or ssh into the instance, but none of those options work.