Is this your first time deploying Airbyte?: Yes
OS Version / Instance: Linux (Amazon)
Memory / Disk: you can use something like 16Gb / 8 Gb
Airbyte Version: 0.40.10
Source name/version: Zuora alpha 0.1.3
Destination name/version: Snowflake
Step: The issue is happening during sync
I deployed Airbyte on an AWS EC2 instance. I can access the web UI using an ssh tunnel as described in the documentation. But I’d like to assign it a DNS and make it available to the other team members. Is that possible?
This is a good question. I’m not entirely sure but my immediate answer is either that it’s not possible or that it is actually possible but not recommended. Mainly because you don’t really want to expose your private instance Airbyte to the world. I’ll ask the team about this and try to get a more concrete answer for you soon. Just wanted to make you aware that we saw your post here.
Thank you @sajarin .
My goal is not to have a public DNS but a private one to my team or my company. Something that can be reached via a VPN.
I asked my team about this. It is possible, you’d have to use a reverse proxy like nginx or traefik in front of airbyte to assign a URL and route DNS to there. You’ll have to terminate TLS since Airbyte doesn’t support it at the moment. You may also want to consider using ELB.
We don’t have a guide at the moment for any of this, so I imagine some of it will be trial and error. It would be great if you get it to work and come back here to share your findings with the rest of the community. Hope this helps!
Thank you @sajarin . I’ll let you know about it.