I have a couple outstanding issues with sync logging caused by a recent upgrade. I’ve also posted about it in GH discussions, and haven’t had anyone take a look. Can someone let me know a dev that would be familiar with sync logs (specifically for a Kubernetes via helm deployment where logs are stored in AWS [S3]) that I can tag?

I'm sorry, but based on the information provided in the extracts, I don't have specific names of developers who could assist with your issue. However, I can suggest some steps based on the information available. 1. Ensure that your S3 logging configuration is correctly set up. According to the [Airbyte documentation](https://docs.airbyte.com/operator-guides/configuring-airbyte), you need to define several environment variables for S3 logging, including

S3_BUCKET

,

S3_REGION

,

S3_AWS_KEY

, and

S3_AWS_SECRET

. 2. If you're using Helm for deployment, make sure your values file is correctly configured. There's a [discussion on Slack](https://airbytehq.slack.com/archives/C021JANJ6TY/p1674160309884009) where a user shared their environment variable setup for a Kubernetes deployment, which might be helpful. 3. If you recently upgraded Airbyte, there might be some changes that affect logging. The [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm) mentions that starting from

0.39.37-alpha

, Airbyte has separated all components into their own independent charts, which might affect how logging is set up. 4. If you're still facing issues, it might be helpful to downgrade to a previous version of Airbyte, as suggested in a [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1674160309884009). If these steps don't resolve your issue, I recommend reaching out to the Airbyte community on [Slack](https://airbytehq.slack.com) or [GitHub](https://github.com/airbytehq/airbyte) for further assistance.

The issues are here and here

we are facing the same issue in version 0.50.27. Also noticed that Log4jAppender is not able to initialise due to misconfiguration of S3 endpoint along with S3 region -- which is not allowed by Aws SDK. This could be because of default " " being initialized for minio and not filtered out in case S3 logging is selected. Have raised issue for the same. https://github.com/airbytehq/airbyte/issues/30189