[GitHub] [camel-kafka-connector] oscerd commented on issue #1272: Using kinesis sink with STS assumeRole credentials?

oscerd commented on issue #1272: URL: https://github.com/apache/camel-kafka-connector/issues/1272#issuecomment-1205426372 No, it's not responsability of the component to support all the credentials provider. Why the component should bring another jar, if not used? The point is having the d

[GitHub] [camel-kafka-connector] oscerd commented on issue #1272: Using kinesis sink with STS assumeRole credentials?

oscerd commented on issue #1272: URL: https://github.com/apache/camel-kafka-connector/issues/1272#issuecomment-1205400090 I don't quite get where do you want to add the sts bits -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [camel-kafka-connector] oscerd commented on issue #1272: Using kinesis sink with STS assumeRole credentials?

oscerd commented on issue #1272: URL: https://github.com/apache/camel-kafka-connector/issues/1272#issuecomment-950325437 > > You can use the credential provider chain of all the AWS Client, by enabling the defaultCredentialProvider option and adding the correct jars in an extended connect

[GitHub] [camel-kafka-connector] oscerd commented on issue #1272: Using kinesis sink with STS assumeRole credentials?

oscerd commented on issue #1272: URL: https://github.com/apache/camel-kafka-connector/issues/1272#issuecomment-946364589 You can use the credential provider chain of all the AWS Client, by enabling the defaultCredentialProvider option and adding the correct jars in an extended connector.