raghav
06/03/2024, 9:39 AMKartik Khare
06/03/2024, 10:01 AMraghav
06/03/2024, 11:17 AMMayank
raghav
06/03/2024, 5:05 PMraghav
06/03/2024, 5:07 PMKartik Khare
06/03/2024, 5:13 PMAdd the following to table config
"security.protocol": "SASL_SSL",
"sasl.mechanism": "AWS_MSK_IAM",
"sasl.jaas.config": "software.amazon.msk.auth.iam.IAMLoginModule required awsRoleArn=\"YOUR_ROLE_HERE\";",
"sasl.client.callback.handler.class": "software.amazon.msk.auth.iam.IAMClientCallbackHandler"
Replace YOUR_ROLE_HERE with the attached AWS role to your pods
Ensure that EC2 role should have AmazonMSKFullAccess and AWSMSKReplicatorExecutionRole permissions (in some cases sts-full-access might also be needed).
The Role's trust relationship in AWS should also allow the following principle
"AWS": "arn:aws:sts::{ACCOUNT_ID}:assumed-role/{ROLE_NAME}/{ROLE_SESSION_NAME}"
Generally the ROLE_SESSION_NAME corresponds to the instance id. In that case, you will need to put all the instanceIDs in the principle
OR
you can simply do "AWS": "*"raghav
06/03/2024, 5:16 PMAnuj Gupta
08/13/2024, 3:45 PMAnuj Gupta
08/13/2024, 3:45 PM