We're also wondering about an issue getting Prefect (local and Cloud) tied in with a self hosted Airbyte instance. That self hosted Airbyte is behind our VPN. When I'm running local Flows on a local Prefect, I can have it kick off a sync on a local Airbyte instance on my machine, but a request to our hosted Airbyte times out. I'm trying to figure out how to solve this. I think the issue is that even running a local Prefect server, there is some server/IP that needs access into our hosted Airbyte? Would self hosting Prefect help solve this? I think our big concern about poking a hole in our VPN is that Airbyte self hosted doesn't have much for auth options

What matters here is where your flow runs, not where the Prefect server is. The orchestration happens entirely separate from the flow execution, so you'd just want your flow runs happening on the same network that your Airbyte server lives on.

Got it... so seems like there's some issue with our VPN config around my local machine talking to self-hosted Airbyte programmatically, and not related to Prefect server. Ill work with our platform team on this, we generally try to lock down a lot of ingress.