oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-1007159162
The component working in the connector is here:
https://github.com/apache/camel/tree/camel-3.11.x/components/camel-aws/camel-aws2-s3
You can look at the code the
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-969937238
> Thanks @oscerd and @scholzj. After some thought, we've decided to use keys
instead of the service account role. The process of using service account role
was too comp
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-957891316
--
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
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-957891316
--
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
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-957946936
If you deploy the connector the error could be related only to the startup
of AWS S3 client. So it's definitely a connector exception.
--
This is an automated message
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-957922331
I don't get what you mean
--
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 t
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-957898434
By the way the error seems to suggest you cannot assume the role so the
error is different. Check your settings in aws
--
This is an automated message from the Apache
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-957891316
For the useDefaultCredentialsProvider option use the camel.source.endpoint
option and not the camel.component one. Also try with the latest release
--
This is an auto
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-950328602
> > I don't think you can do in that way, you need to build a tar.gz
connector self-containing STS jar in the same folder, so in the plugin path
you'll have a directory
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-950326617
By the way before going with this approach, maybe you should try to build a
local connector and run kafka connect locally
--
This is an automated message from the Apa
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-950325712
My suggestion is pushing the connector on one custom maven central groupId
if there is no other way, but maybe @scholzj can suggest some approach.
--
This is an autom
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-946360426
I don't think you can do in that way, you need to build a tar.gz connector
self-containing STS jar in the same folder, so in the plugin path you'll have a
directory for
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-936073373
Essentially you need to add the STS jar
(https://search.maven.org/artifact/software.amazon.awssdk/sts) in your zipped
connector or in the exploded folder once it has be
oscerd commented on issue #1263:
URL:
https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-933777804
You need to add the sts jar to your connector folder related to S3 in plugin
path
--
This is an automated message from the Apache Git Service.
To respond to the messa
14 matches
Mail list logo