Hello all!
I posted a
msg in the
#replication-troubleshooting channel, but was able to track down what I believe to be the root cause of the issue. It seems to be a simple dependency version bump could be the trick.
I found
this github issue in the aws-sdk-java repo addressing how the java v1 sdk does not work with EKS Pod Identity add-on. It seems that a recent update to the sdk in June of this year has added the required support to version 1.12.746 of the sdk.
Checking the java aws sdk version in the airbyte repos, I see that it would simply be a patch version bump in both cases to bring it up to the version required for pod identity support.
airbyte
airbyte-platform
I would love to be able to contribute this but have never contributed to airbyte before. I read the contributing guidelines, but wasn't sure which repo I should create an issue in? Or does it matter? Would a version bump like this be addressed quickly? I am working on a time sensitive project and if I could contribute this and have it available in official builds quickly I would be very motivated to get it done.