-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support AWS IRSA. #140
Comments
I'll look into it. |
I looked at the conversation you cited. The S3 access key and secret key are indeed optional. In fact, it's safer to not use them but instead use the IAM roles set up for your processes. There was a question of whether they can be blank. Currently setting them to blank certainly will not work because the code only checks for log4j-s3-search/appender-core/src/main/java/com/van/logging/aws/AwsClientHelpers.java Line 16 in 90317ec
log4j-s3-search/appender-core/src/main/java/com/van/logging/utils/StringUtils.java Line 15 in 90317ec
|
Anyway. from the conversation, it looks like this is not an actual issue for your setup; I believe there was a confusion over whether the Let me know if this is not the case. |
Hi @bluedenim !
Thanks again for the great plugin. We at Airbyte love this. I'm wondering if you know whether this plugin supports IRSA.
We have several OSS community members interested in getting this working: airbytehq/airbyte-platform#263. I'm not sure if IRSA works well with this plugin now, and I would prefer to contribute back than roll our own.
We are happy to take pointers & submit a contribution.
Thanks!
The text was updated successfully, but these errors were encountered: