I’m evaluating the Airbyte open source version on AWS to replace another ELT tool we use and I’m happy with it so far even though some of the connectors are in alpha. I wonder how you use it for the prod environment. Does anyone use it on an EC2 with Docker for prod? How has your experience been so far? What kind of deployment do you recommend?

Hi. We use this method and I recommend the one that works best for you 🙂 We dont use dev source or connection but rather we build a new one that works best for us

@[DEPRECATED] Marcos Marx turned this thread into Zendesk ticket 2619 to ensure timely resolution!

Thanks again for your input, Eli! Murat, here is the documentation on how to deploy Airbyte on EC2: https://docs.airbyte.com/deploying-airbyte/on-aws-ec2

Thanks @Octavia Squidington III . I followed this great documentation and deployed Airbyte already. I was wondering if other users have a different approach for prod environment.

@Murat Cetink, we initially launched on an EC2 for production but ran into some resource issues after a bit. However, we're using to sync a large volume of connectors (50+ connections) with heavy amounts of data (we're an agency) so we had to migrate to K8. However, when we were running it with just 5 to 10 connections, the EC2 worked just fine. One suggestion I'd make is migrating to a standalone Postgres server sooner rather than later. It is helpful to have easier access than having to connect the docker container and it allows for backups.