topic AWS Application Load Balancer Health Check Qlik Sense in Management & Governance

AWS Application Load Balancer Health Check Qlik Sense

maheshyv — Sat, 16 Nov 2024 05:54:14 GMT

I'm trying to Use AWS Application Load Balancer, by health Check is always UnHealthy. When i use Network Load Balancer Node become healthy i used TLS 443. But when i use Application ELB i need to specify Path. I tried with all possible combinations like /engine/healthcheck or /mynodename/hub or / but it's always unhealthy on port 443. Any suggestions on how to make it healthy?

Re: AWS Application Load Balancer Health Check Qlik Sense

witty — Tue, 07 May 2019 12:51:05 GMT

try using a new application load-balancer and a target group; then you can specify the status codes that are "healthy"

Re: AWS Application Load Balancer Health Check Qlik Sense

maheshyv — Tue, 07 May 2019 13:17:51 GMT

it worked

Re: AWS Application Load Balancer Health Check Qlik Sense

Levi_Turner — Tue, 07 May 2019 14:13:57 GMT

/qps/user with a 201 should also be healthy. Can you give that a try? The accepted answer, albeit correct, will have a consequence of spamming Qlik's logs with attempted authentication attempts.

Re: AWS Application Load Balancer Health Check Qlik Sense

witty — Tue, 07 May 2019 14:37:32 GMT

@Levi
This is good to know; - 201 (201 Created) did not result in healthy state but using 200 and that path does.

Re: AWS Application Load Balancer Health Check Qlik Sense

Levi_Turner — Tue, 07 May 2019 14:38:57 GMT

Doh, yeah, it should be a 200 (OK) response 😃

Re: AWS Application Load Balancer Health Check Qlik Sense

maheshyv — Tue, 07 May 2019 14:55:35 GMT

/qps/user and status code -200 is healthy 🙂