I have a Jenkins CI server in a private VPC EC2 subnet, and in order to make it accessible from the outside world, I configured ELB (which also processes the HTTPS security certificate using IAM, but this is just the rationale for why I am doing this, and not accessing one instance directly).
The Jenkins server is configured for authentication, so when ELB performs its health check as an anonymous user, it receives a restricted page with 403 access, which should be fine, but understood as an error, and this flag is marked as not working.
Is there any way to get ELB to treat 403 response as OK response? Or maybe there is a page in Jenkins that always returns a 200 status code?
source
share