it’s something related to the minio logs config when logging to S3. Does anyone know how to configure it? I’m facing the same issue (Tested with BQ & Redshift as target), and the error logs don’t print out the name of the bucket that airbyte is trying to connect to

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2723 to ensure timely resolution!

Hey could you help more with the usecase?

Sure, how can I help? Do you need logs or something like that?

Yeah that will be very helpful

These are the logs for one of the attempts

Hey to confirm it is working with minio without s3?

We've stopped trying to make it work. We moved to Airbyte on K8 using Plural. That works very well

👍

I am facing the exact same issue that @Ahmad Zamrik mentioned, yes minio was working without S3 how can i configure logging into S3?

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

yes

Hey @Krishna Elangovan, I know it’s been a while. We have a part in our docs about setting up S3 logging: https://docs.airbyte.com/deploying-airbyte/on-kubernetes/#configuring-custom-s3-log-location Let me know if this helps

I have followed that doc already it does not work and since i am using the helm chart the doc does not explain about setting the S3 logging on the helm docs

Hey Krishna, does minio logging work with your helm setup? I believe it should be a similar procedure outlined in the doc above even if it's not helm specific