- Newest
- Most votes
- Most comments
Hello ,
To help you with regards to this issue and to know the root cause of the issue I would suggest you to :
1: To identify the cause of the health events and for more detailed information about the current environment's health, I would suggest you to please to open the Health page by choosing Causes. Alternatively, in the navigation pane, choose Health . For more details please refer [1]
2: I would also suggest you to please follow the steps mentioned in this reference link 2 which will be helpful for you to troubleshoot an Elastic Beanstalk environment health status . Moreover please take a look into this reference link[3] which will help you determine the Factors in determining instance and environment health.
3: Moreover I would suggest to check the reference link 4 for troubleshoot ELB health checks with Elastic Beanstalk and please check the beanstalk environment log[5] file which will help you to know the root cause of the issue .
Lastly if wish to have a extended investigation on the any specfic environment events observed in your beanstalk environment , please feel free to reach out to us via AWS Support case , we will be always happy to help you further .
Reference link : [1] Enhanced health monitoring with the environment management console - Environment overview - https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/health-enhanced-console.html#health-enhanced-console-overview
[3] Enhanced health reporting and monitoring - Factors in determining instance and environment health - https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/health-enhanced.html#health-enhanced-factors
[5] Viewing logs from Amazon EC2 instances in your Elastic Beanstalk environment - https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.logging.html
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago