jc43081 opened a new issue #1331: URL: https://github.com/apache/camel-kafka-connector/issues/1331
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](https://github.com/apache/camel-kafka-connector/blob/camel-kafka-connector-1.0.x/connectors/camel-aws-kinesis-sink-kafka-connector/src/main/java/org/apache/camel/kafkaconnector/awskinesissink/CamelAwskinesissinkSinkConnectorConfig.java). As outlined within [AWS documentation](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html), 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](https://github.com/apache/camel-kafka-connector/blob/camel-kafka-connector-0.11.x/connectors/camel-aws2-kinesis-kafka-connector/src/main/java/org/apache/camel/kafkaconnector/aws2kinesis/CamelAws2kinesisSinkConnectorConfig.java). 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! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
