Hi folks! QQ, when setting up S3 as a destination, is there any docs on how to use IRSA instead of the basic Auth: AWS Key and ID ? We need to use IAM roles or in this case since Airbyte is deployed to EKS: IRSA. Also having this same problem with setting up Airbyte logging bucket for S3. I am running on

0.40.0-alpha

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

I also think the most important thing is the logging bucket since configuring this successfully will allow us to create other connections to unblock other workflows. If anyone has successfully configured S3 logging bucket using IRSA, any insights would be great. Also wondering if that is even possible in 0.40.0-alpha

Hey there, I believe support for IRSA should have been added in S3 destination version v0.3.10: https://github.com/airbytehq/airbyte/pull/14231

This new provider uses DefaultAWSCredentialsProviderChain which looks for credential in the following order:
...
- Web Identity Token credentials from the environment or container

My understanding is that if the service account JWT is mounted in the environment, it should be able to find and use the credential? For the logging bucket however, it looks like we still have an open issue on this. https://github.com/airbytehq/airbyte/issues/5942