oscerd commented on issue #1311: URL: https://github.com/apache/camel-kafka-connector/issues/1311#issuecomment-6632137724
Closing this as a how-to question, with apologies that it was never answered. The 0.x `CamelAws2s3SourceConnector` is gone; with `camel-aws-s3-source-kafka-connector` 4.22.x you can keep the keys out of the KafkaConnector YAML with a Kafka Connect config provider, for example Strimzi's `KubernetesSecretConfigProvider` (https://github.com/strimzi/kafka-kubernetes-config-provider) and `camel.kamelet.aws-s3-source.accessKey: ${secrets:<namespace>/<secret>:<key>}`, or a `FileConfigProvider` over a mounted secret. Kafka Connect resolves these references when the connector (re)starts, so a rotated secret is picked up on the next connector restart; alternatively, `camel.kamelet.aws-s3-source.useDefaultCredentialsProvider=true` with an IAM role for the Connect service account avoids static keys altogether. Broader documentation on credentials is being discussed in #1785; if something does not work on 4.22.x, please open a new issue with your config and stack trace. --- _Claude Code on behalf of Andrea Cosentino_ -- 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]
