what are the values i need to set in the helm chart in order to get s3 logging to work?

To set up S3 logging in the Helm chart for Airbyte, you need to define several values in the

values.yaml

file. Here are the values you need to set: 1.

S3_BUCKET

- Define the S3 bucket to store logs. 2.

S3_REGION

- Define the S3 region the S3 log bucket is in. 3.

S3_AWS_KEY

- Define the key used to access the S3 log bucket. 4.

S3_AWS_SECRET

- Define the secret used to access the S3 log bucket. 5.

S3_MINIO_ENDPOINT

- Define the URL Minio is hosted at so Airbyte can use Minio to store logs. 6.

S3_PATH_STYLE_ACCESS

- Set to

true

if using Minio to store logs. Empty otherwise. You can find more information about these values in the [Airbyte documentation](https://docs.airbyte.com/operator-guides/configuring-airbyte). If you are migrating from old charts to new ones, you need to update your configuration so you can continue to use your custom logging. Declare a global value in

values.yaml

file and move everything related to logging under that section. After updating

values.yaml

, upgrade your chart by running the command:

bash helm upgrade -f path/to/values.yaml %release_name% airbyte/airbyte

You can find more information about this in the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm). Please note that Airbyte does not support logging to separate Cloud Storage providers.

Does logging support leveraging IRSA for the AWS service account