What is the recommended AWS EC2 instance type for running Airbyte OSS version 1.1.0 via abctl ? I’ve reviewed the documentation, but I feel the resource recommendations might not be accurate. Could anyone share which EC2 instance type has worked well for them with Airbyte OSS version 1.1.0 ?

Based on the provided knowledge sources, here are the recommendations for running Airbyte OSS via abctl on AWS EC2: For the best performance, Airbyte recommends running on a machine with at least 4 CPUs and 8 GB of RAM [Documentation > Using-airbyte > Getting-started > Quickstart](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart#suggested-resources). This is equivalent to a t2.large instance when using the

--low-resource-mode

flag. However, there are some conflicting reports and discussions about the actual resource requirements: 1. Some users have reported success with 8 GB RAM, even if the CPU count is lower [Github Issue (closed)](https://github.com/airbytehq/airbyte/issues/40231). 2. For testing purposes, a t2.medium might be sufficient, while a t2.large is recommended for production environments [Forum Post: Deploy EC2: Slow runtime on t3.micro](https://discuss.airbyte.io/t/2334). 3. In some cases, users have needed to use larger instances. One user reported using a t4g.2xlarge for running extracts and loads [Github Issue (closed)](https://github.com/airbytehq/airbyte/issues/40231). 4. For enterprise setups, Airbyte recommends memory-optimized instances such as M7i / M7g instance types [Documentation > Enterprise-setup > Implementation Guide](https://docs.airbyte.com/enterprise-setup/implementation-guide#prerequisites). It's important to note that the actual requirements may vary depending on your specific use case, the volume of data you're processing, and the complexity of your syncs. If you're experiencing performance issues or instability, you might want to consider using a larger instance type than the minimum recommendations. Some users have reported better stability with larger instances like t2.xlarge [Forum Post: Crashing, freezing, corruption / lost data](https://discuss.airbyte.io/t/3715). Given the variability in user experiences, it might be worth starting with a t2.large (or equivalent) and monitoring performance, then adjusting as needed based on your specific workload.