-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Destination Iceberg V2: support aws instance profile auth #50876
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
37c4d02
to
0b42c56
Compare
For the eventual reviewer, I was able to test this and successfully authenticate via an IAM instance role without providing the IAM key and secret using the |
airbyte-cdk/bulk/core/load/src/main/kotlin/io/airbyte/cdk/load/check/CheckOperation.kt
Show resolved
Hide resolved
|
||
// If we don't have explicit S3 creds, fall back to the default creds provider chain. | ||
// For example, this should allow us to use AWS instance profiles. | ||
val awsAccessKeyId = config.awsAccessKeyConfiguration.accessKeyId |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine but now that I see this behavior, I think you are right, we should use that pattern for the Assume role path. I don't think we should make the change in this PR though
this seems to work:
also, updates the CDK to log the throwable during a
check
failure. afaict platform doesn't expose the trace message, and I don't know if we actually want to dump the full stacktrace into the check status message.@frifriSF59 lmk if you already have something like this as part of https://github.com/airbytehq/airbyte-internal-issues/issues/11082 though
(take from beta channel https://airbytehq-team.slack.com/archives/C087GAG7X25/p1735921337428349 )