Hi there! Is there an unauthenticated health check endpoint that can be used with Airbyte Open Source? I have Airbyte deployed on an EC2, fronted by an ELB, however the Target Group is currently evaluating the health of the Airbyte instance and receiving a 401 from

/v1/health

.

🤔

/v1/health

does not require any authentication: https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html#get-/v1/health Can you share the full error?

Hi @Sunny Hashmi (Airbyte) thanks for your reply. Simple example here using

curl

on the EC2 instance itself. Am I missing something here?

root@airbyte ~]# curl -I localhost:8000/v1/health
HTTP/1.1 401 Unauthorized
Server: nginx/1.23.2
Date: Wed, 09 Nov 2022 01:00:35 GMT
Content-Type: text/html
Content-Length: 701
Connection: keep-alive
WWW-Authenticate: Basic realm="Welcome to Airbyte"
ETag: "6361a6dc-2bd"

Hmm, maybe related to this: https://github.com/airbytehq/airbyte/issues/18245 Disabling basic auth may help, some info here in the readme.

Thanks @Sunny Hashmi (Airbyte), unfortunately AWS ELB doesn’t support basic auth for health checks, and disabling auth to the application isn’t ideal. Besides accepting

401

as a “healthy” response, do you have any other suggestions?

I can't think of any other workarounds at the moment, sorry 😞 airbyte-proxy is still pretty new and we're ironing out the wrinkles. This may come up for others too, could you create an issue in the repo so that we can look more closely at improving this?

Hey @Lachlan Wells, did you solve this error??? We are also trying to set the ALB up and stuck at the same issue, Health Checks are failing continuously...