My Elastic Beanstalk application is in a constant
severe state... even though it's working absolutely fine.
Looking at the Health screen it says that 100% of its requests are
3xx, and looking at the logs, this is apparently confirmed:
[29/Nov/2017:10:07:46 +0000] "GET / HTTP/1.1" 302 356 "-" "ELB-HealthChecker/2.0"
This makes perfect sense, as
/ will 302 Redirect you to the "login" page.
The thing is, I've told AWS to NOT use
/ when checking for health, but instead to use
/news which should always return a
200, whether you're logged in or not:
I've tried changing the Health check URL to other suitable endpoints, and restarting the EC2 instance, but it always returns to checking
/ (according to the logs). I've given it 12 hours to see if it would change in time, too.
So why does it keep checking
/ and returning a
severe state? What can I do to fix this? Is it a Security Group issue perhaps (even though the site is open to the public)?