Value is not one of the allowed values: [Ok, Warning, Degraded, Severe]
I have an Elastic Beanstalk application, and I am trying to upload and implement a new version of it, but I am getting the following error when try to.
But the integrity of the system seems to be ok, as in the image below:
Also, I realized that there were previously some warning and it was transitioning from Ok to Severe, and then back to Ok....
Looking at the access.logs from nginx seems to be fine.
Please, any help on that? can't seem to find any related issue anywhere...
EDIT:
I found some logs at access.log in nginx that are throwing 403:
- Newest
- Most votes
- Most comments
Are there any problems with the health check paths, etc. used by Elastic Beanstalk's load balancer?
If the wrong health check path is set, such errors will occur, such as 404 errors.
In addition, the following documents provide general troubleshooting instructions.
Please check once.
https://repost.aws/knowledge-center/elastic-beanstalk-yellow-warning
I understand from your follow-up question that you have concerns about some 403 errors in the logs. Elastic Beanstalk enhanced health reporting relies on a set of rules to determine the health of your environment. Some of these rules might not be appropriate for your particular application. By default, Elastic Beanstalk includes all application HTTP 4xx errors when determining the environment's health. You can choose to ignore application HTTP 4xx errors on the environment's instances, or to ignore HTTP 4xx errors returned by the environment's load balancer. Reference: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/health-enhanced-rules.html
Regarding your initial error message on the banner in your console, you may refer to following doc for details on this specific namespace and the permitted option-settings. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-elasticbeanstalkhealthreporting
Relevant content
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated a year ago
Thank you very much for the answer! Looking at what you provided and answer, seems that there is no issue with the health check paths as far as I could check, but now looking further in the logs I realized there are some 403 being logged, I attached the image of the log in the EDIT of this question, do you have any why this is happening?