API airbyte oddness

Trying to pull instapage api with airbyte, getting a cloudflare 403 challenge from instapage’s end. But it’s really odd:

When testing the stream in connection builder in Airbyte cloud it throws a 403 (so does the test call when creating a source)

However with Airbyte on an ec2 deployed with abctl, while the source creation still throws the 403, testing the api in connection builder actually works

I can’t understand why the connection builder call goes through, but the other place where it makes the same exact http call fails with a 403. I used beeceptor to confirm the headers passed are exactly the same. Silver lining, beeceptor offers to forward the calls it receives to the target api, basically an active proxy, and using that it worked even with airbyte cloud. I was going to try to like add a proxy to the ec2 airbyte is running on and just use that to forward the calls.