Enables developers to use AWS Identity and Access Management (IAM) to connect to their Amazon Managed Streaming for Apache Kafka (Amazon MSK) clusters.
Apache License 2.0
137
stars
65
forks
source link
Add support for explicit access key and secret in sasl.jaas.config #98
We have a somewhat narrow use case where we want to run MirrorMaker 2 (MirrorSourceConnector) on MSK Connect to replicate between two clusters in two separate AWS partitions (Global and China). Because they are in different partitions, the normal approach of cross account role trusts is not feasible. Because there are two IAM contexts needed in the same process, the standard AWSCredentialsProfiderChain does not work, nor any of the existing workarounds. All the provided overrides affect all kafka clients in the process. Specifying awsProfileName would work, except there is no way to deploy profile configuration into MSK Connect.
We need a way to specify sufficient configuration inline to authenticate the client.
We have noticed this issue has not received attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.
We have a somewhat narrow use case where we want to run MirrorMaker 2 (MirrorSourceConnector) on MSK Connect to replicate between two clusters in two separate AWS partitions (Global and China). Because they are in different partitions, the normal approach of cross account role trusts is not feasible. Because there are two IAM contexts needed in the same process, the standard AWSCredentialsProfiderChain does not work, nor any of the existing workarounds. All the provided overrides affect all kafka clients in the process. Specifying awsProfileName would work, except there is no way to deploy profile configuration into MSK Connect.
We need a way to specify sufficient configuration inline to authenticate the client.