Summary
User is experiencing a 403 error when saving a connection in Airbyte deployed behind an AWS ALB on EKS, while it works via port forwarding. The issue may be related to authentication settings or routing configurations for the API.
Question
I am deploying airbyte behind an AWS ALB from EKS. I can get to the UI just fine over the ALB, but any time i attempt to save a connection, i get a lovely 403. When i do it via a port forward the same connection works just fine from what i can tell. So i’m assuming there is something auth related that is having issues communicating with the api server. Most of the settings on the ALB like preservation of client port, x-forward-for headers, preserving host headers, etc are all enabled. Routing is /* and a http://HOSTNAME.DOMAIN.COM|HOSTNAME.DOMAIN.COM (so i can’t imagine I’m missing requests). My understanding of the architecture was that just the webapp needed to be exposed. Do I also need to add the api into the path routing? If so, what is the root path?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.