@kapa.ai What is the ideal resource requirement for Airbyte v1.5.5 in a production-grade EKS environment?

The knowledge sources don’t provide version‑specific sizing for Airbyte v1.5.5, but they do give general production guidance for Self‑Managed Enterprise on Kubernetes/EKS that you can safely apply. From the implementation guides (v1.6–2.1) and the generic Enterprise guide, a production‑grade EKS setup for Airbyte should have at least: 1. Kubernetes / EKS cluster ◦ Amazon EKS on EC2 (Fargate is not supported). ◦ Nodes in 2+ Availability Zones. ◦ Minimum 6 nodes in the cluster for a production deployment. [Infra prereqs 2.0; Infra prereqs (generic)] 1. Node instance type & size ◦ Use memory‑optimized instances (e.g. M7i / M7g families). ◦ Each node should have at least 2 vCPUs and 8 GiB RAM. [Infra prereqs 2.0; Infra prereqs 2.1] 1. Disk / storage ◦ Allocate ≥ 30 GiB disk per node to comfortably hold connector images and logs. [Scaling operator guide] 1. Pods / concurrency capacity ◦ Ensure the cluster can schedule roughly

2 × <number-of-possible-concurrent-connections>

pods at once as a rule of thumb. [Scaling operator guide] 1. Other required components ◦ Ingress: e.g. AWS ALB for UI/API access. ◦ Object storage: S3 bucket with directories for logs and state. ◦ Database: Dedicated Postgres (e.g. Amazon RDS) with at least one read replica. ◦ Secrets: External secrets manager (e.g. AWS Secrets Manager). [Infra prereqs 2.0] Because none of the documents cover v1.5.5 specifically, you should treat these as baseline minimums and then scale node count and connector resources based on your actual sync concurrency and workload characteristics. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.