I’m looking to deploy Airbyte on AWS in production. We have a fairly large dataset with about 500 million monthly active rows. We are debating between using EKS or EC2. In general, which of these is easiest to manage? Which is more likely to be able to scale to meet our needs?

I've on the EC2 but seeing some issues with the port/SG rules. - using the docker engine on the EC2 itself. Not EKS.

@A BK Yeah, my initial experience with EC2 was a lot of networking problems, but that probably has a lot to do with our somewhat complicated VPC setup. I eventually got it working, but we will see if it scales well. The EKS version was definitely more complicated, at least for me with no prior K8s or EKS experience. For reference, these are the EKS docs

Hello Zander Otavka, it's been a while without an update from us. Are you still having problems or did you find a solution?

We opted not to go with airbyte because the DBT normalization phase was way too slow. Even with WAL replication, syncs were taking upwards of 8 minutes and consuming a lot of snowflake resources. Fivetran syncs only take 2-3 minutes at most