Andrea Cosentino

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.

By the way before going with this approach, maybe you should try to build a local connector and run kafka connect locally

> > 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...

For the useDefaultCredentialsProvider option use the camel.source.endpoint option and not the camel.component one. Also try with the latest release

By the way the error seems to suggest you cannot assume the role so the error is different. Check your settings in aws

I don't get what you mean

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.

> 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 complicated and...

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 there.

The 1.0.x release has been based on Kamelets and in particular on source and sink. https://github.com/apache/camel-kamelets/blob/main/kamelets/kafka-source.kamelet.yaml https://github.com/apache/camel-kamelets/blob/main/kamelets/kafka-sink.kamelet.yaml The old 0.11.x has been based on plain camel componet and so you...