From 4dd8e37294d1c46925d0c4e98e9ab923913a0320 Mon Sep 17 00:00:00 2001 From: rustagir Date: Mon, 24 Jun 2024 13:13:30 -0400 Subject: [PATCH] fix --- source/security-and-authentication/custom-auth.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/security-and-authentication/custom-auth.txt b/source/security-and-authentication/custom-auth.txt index 18e75fdd..8c319630 100644 --- a/source/security-and-authentication/custom-auth.txt +++ b/source/security-and-authentication/custom-auth.txt @@ -72,13 +72,13 @@ by using AWS IAM authentication: "value.converter.schemas.enable": false, "database": "", "collection": "", - "mongo.custom.auth.mechanism.enable":"true", - "mongo.custom.auth.mechanism.providerClass":"com.mongodb.SampleAssumeRoleCredential", - "mongodbaws.auth.mechanism.roleArn":"arn:aws:iam::99999999:role/KafkaAtlasRole" + "mongo.custom.auth.mechanism.enable": "true", + "mongo.custom.auth.mechanism.providerClass": "com.mongodb.SampleAssumeRoleCredential", + "mongodbaws.auth.mechanism.roleArn": "arn:aws:iam::99999999:role/KafkaAtlasRole" } } In this example, the ``roleArn`` value is the IAM Role of the user group that has -access to MongoDB Atlas. In the AWS IAM console, we gave ``AssumeRole`` -permissions on the IAM account that is running {+kafka-connect+} to this -Atlas Group IAM Role. +access to MongoDB Atlas. In the AWS IAM console, the IAM account that is +running {+kafka-connect+} has ``AssumeRole`` permissions to this Atlas +Group IAM Role.