Support ALB health check endpoint
chadmyers opened this issue · 1 comments
I'm trying to run the aws-sigv4-proxy behind an ALB as an ECS Fargate service and when the load balancer hits the service it connects to HTTP / and the proxy returns a 502 Bad Gateway. ALB only supports HTTP status codes 200-499 so there's no way for me to add a health check to the proxy for "signs of life".
Could we add a /aws-sigv4-proxy-healthcheck endpoint or something like that that returns 200 if the proxy is up and listening?
I was able to work around this by setting both the --host and the --sign-host to be the CloudSearch domain's "doc-search" URL hostname. Now when the healthchecker hits /, the proxy sends that to cloudsearch which returns a 403 access denied (which is correct) and I can set the health check to look for 403 responses.
I think this is actually preferable to having a separate dummy response in the proxy for health check as this sends a request all the way through to cloudsearch which tests that everything is working and is a good health check. Closing now.