Hello everyone! Hope you're all doing well. I have this very same issue running Airbyte using kustomize on AWS EKS on version 0.40.21 https://github.com/airbytehq/airbyte/issues/18016 Has anyone had success trying to resolve the issue using s3? Thanks!

we are able to use s3 for state and logs with airbyte helm version 0.40.46 on AWS EKS. This helm version uses airbyte system version 0.40.18. unless you have to use kustomize, you can try helm.

Thank you @Shangwei Wang. The helm chart is still in beta phase hence taking the kustomize route. Appreciate the help 🙂

no problem. we actually were trying kustomize, and ran into some similar issue, so we switched to helm. These tools to me mostly are just kubernetes manifest tools, so as long as the final artifacts (manifests) are working, I’m not super worried using one versus the other at the moment.

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