camel-kafka-connector
camel-kafka-connector copied to clipboard
apache
AWS Default Credential Provider is no longer available in 1.0?
Previous to 1.0, the Default Credential Provider was able to be used for security credentials when connecting to AWS. It appears that with the pivot to Kamelets that this functionality is no longer available and the only supported method is accesskey and secret. As outlined within AWS documentation, the recommended method is to use the Default Credential Provider since it allows the most flexibility.
Our company doesn't allow use of access keys and secrets but requires token based credentials. The previous implementation supported this just fine. Support of Default Credential Provider is essential to our continued adoption.
Is functionality planned to be added back in? If yes, when can it be expected? Thanks!
It needs to be done at kamelet level in this case. Let me open an issue there
That's exactly what we noticed as well. We are using the SNS Kafka connector For AWS2 version 0.9 and it doesn't work if we don't provide explicit aws access key and secrets properties. The docs do not say what needs to be done to use the Default (EC2 based for instance) credentials providers. Assuming your changes just merged in Kamelet do fix that issue, what do we need to do to get it working ? Thank you!
If you use the default credential provider parameter, the order will be the following: https://github.com/aws/aws-sdk-java-v2/blob/2.17.118/core/auth/src/main/java/software/amazon/awssdk/auth/credentials/DefaultCredentialsProvider.java#L24
It's up to you to satisfy one of this condition.
By the way, the fix is not completed, and for sure, we'll need a new ckc release for 1.0.x
Hi, is there any updates on this issue? Seems the https://github.com/apache/camel-kamelets/issues/735 was already resolved
We need to release 0.8.0 of camel-kamelets officially and after that we are going to release a version of camel-kafka-connector supporting it.