1 Answer
- Newest
- Most votes
- Most comments
0
Hi, even though your option is console, I would suggest you to execute a few EB CLI commands in the hope to obtain additional error messages pointing to the root cause:
aws elasticbeanstalk describe-events --environment-name my-env
aws elasticbeanstalk describe-environment-health --environment-name my-env --attribute-names All
aws elasticbeanstalk describe-environments --environment-names my-env
aws elasticbeanstalk describe-applications
For all details, see https://awscli.amazonaws.com/v2/documentation/api/latest/reference/elasticbeanstalk/describe-environment-health.html
Such commands may provide more details than the console on the root cause of your problem. In particular, describe-events may help you spot the moment where it started with a corresponding event.
Best,
Didier
Relevant content
- asked 2 years ago
- asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- How do I customize my nginx configuration to modify the "client_max_body_size" in Elastic Beanstalk?AWS OFFICIALUpdated a year ago
Thanks, Didier! I'll try with the commands and let you know! Much appreciated :)