Hey! I am using Prefect 1.0 as my orchestration to...
# replication-troubleshooting
c
Hey! I am using Prefect 1.0 as my orchestration tool at the moment and I am keen to understand how I can integrate an Airbyte Instance on EC2 to Prefect Cloud deployment using ECS Fargate for execution. Inline with the security suggestions, it doesn’t allow inbound traffic from the internet. My only other idea was to create a ALB for Fargate so I can have an IP I can configure on the EC2 instance inbound rules. Would love to hear if there is a solution that doesn’t involve adding infra elements or if there i just a better way to handle this.
Trying out just adding the security group from the ECS Cluster/Task on the inbound rules of the Airbyte EC2 instance
s
Yeah, for the moment most users are doing either nginx reverse proxy in front of it on the same box, or an ALB. We are planning on implementing nginx by default in open source, but it's still a work in progress. https://github.com/airbytehq/airbyte/issues/17865
This blog is cited pretty often, I have not personally run through it though so ymmv -- please let everyone know if it works out 🙂 https://blog.shadabmohammad.com/deploy-and-secure-airbyte-with-nginx-reverse-proxy-basic-authentication-lets-encrypt-ssl-72bee223a4d9
c
I have gone through the blog. It seemed like a lengthy workaround for me, at least right now. Adding the security group to the inbound rules and using the private IP in the params of the airbyte connection prefect task work as expected. The basic auth or SSO wasn’t a requirement in my case just getting access to the api securely from an ECS task.
s
Oh I see, thanks for explaining! That makes sense and does sound like my suggestion would be overkill. Did the security group do the trick?
c
Yes it did 😃
octavia loves 1