To anyone who is using this repo (it's awesome by the way!), you might be running into some problems with the health of Elastic Beanstalk always being severe.
The source of the issue stems from the checks that the load balancer makes to elastic beanstalk:
# This is a log entry from /var/log/nginx/access_log
XXX.XX.XX.XX - - [24/Apr/2018:02:55:29 +0000] "GET / HTTP/1.1" 301 31 "-" "ELB-HealthChecker/2.0" "-"
The ELB expects by default that the status code returned should be 200. In this case, it's a 301 because of specific setup for the application/website (EG: force redirect to https).
This is caused by the load balancer settings for elastic beanstalk. To edit them:
Go to your elastic beanstalk environment
Select your specific application
Use the sidebar to select "Configuration", then "modify" the Load Balancer.
From "Processes", select the checkbox next to name "default" and use the "Actions" dropdown > "Edit"
The next settings are really specific to your setup, however as an example you can change the port to protocol to be specific to your needs. Basically, make sure the load balancer health check gets the correct status code.
To anyone who is using this repo (it's awesome by the way!), you might be running into some problems with the health of Elastic Beanstalk always being severe.
The source of the issue stems from the checks that the load balancer makes to elastic beanstalk:
The ELB expects by default that the status code returned should be 200. In this case, it's a 301 because of specific setup for the application/website (EG: force redirect to https).
This is caused by the load balancer settings for elastic beanstalk. To edit them:
Hope this helps someone!