To deploy Airbyte on AWS EKS, you can use Helm for deployment. You'll need to create a

values.yaml

file in your local folder and populate it with default configuration override values. An example of the

values.yaml

file can be found in the [charts/airbyte](https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/values.yaml) folder of the Airbyte repository. To customize your deployment, you can modify the

values.yaml

file according to your requirements. After specifying your own configuration, run the following command:

helm install --values path/to/values.yaml %release_name% airbyte/airbyte

[Source](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm) Regarding the physical volume, Airbyte supports logging to Minio, S3, and GCS buckets. To configure a custom S3 log location, you can follow the instructions in the [documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes#configure-the-custom-s3-log-location). For more advanced customization, you can refer to the

values.yaml

file and modify the fields according to your needs. However, the provided information extracts do not cover all possible customizations like ingress configuration. You may need to refer to the official [Airbyte documentation](https://docs.airbyte.com/) or seek help from the [Airbyte community](https://airbytehq.slack.com/) for more specific guidance.

I understand there are several applications that need to talk to each other (according to values.yaml) or not?