basapuram-kumar opened a new issue, #1785: URL: https://github.com/apache/camel-kafka-connector/issues/1785
Currently, Camel Kafka Connectors wrap the Camel AWS2 components, and many enterprise users prefer not to embed long-lived AWS access keys directly in the connector configuration (JSON). Instead, they typically rely on enterprise authentication mechanisms such as: HashiCorp Vault (or Kafka Connect ConfigProvider) for secret management SAML-based authentication that generates temporary AWS credentials (for example, using saml2aws or AWS IAM Identity Center) Other enterprise-recommended authentication mechanisms and best practices At present, AWS Kamelets/connectors expose properties such as accessKey, secretKey, and useDefaultCredentialsProvider. However, we could not find any documented guidance on enterprise authentication patterns or first-class support for secret references (for example, Vault or ConfigProvider) at the connector layer. Has this use case already been considered by the Camel Kafka Connect team? If so, is there any existing guidance or roadmap for supporting these enterprise authentication patterns? If not, would it be possible to consider adding documentation and/or native support for these authentication mechanisms in future releases? Any insights or recommendations on the preferred enterprise approach would be greatly appreciated. -- 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]
