Andrea Cosentino

Is this done with 3.8.0 @orpiske ?

It needs to be done at kamelet level in this case. Let me open an issue there

https://github.com/apache/camel-kamelets/issues/735

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

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.

> Hi @oscerd, will these changes be merged, and if so I will create a new PR to replace this one. It needs to be updated with licenses and aligned...

@valdar I think this would make sense.

@jaapterwoerds thanks for reporting this, I guess we should do something like this in the general Sink connector.

I'd like to revive the discussion. There are number of aws components that don't make sense as connector. For example kms,iam,eks,ecs etc. Also some others. I'd like to limit the...

Let me start by removing these: camel-aws2-ec2 camel-aws2-ecs camel-aws2-eks camel-aws2-iam camel-aws2-kms camel-aws2-mq camel-aws2-msk camel-aws-ec2 camel-aws-ecs camel-aws-eks camel-aws-iam camel-aws-kms camel-aws-mq camel-aws-msk This components have only the producer side and are used...