fix

mongodb · Jun 24, 2024 · 4dd8e37 · 4dd8e37
1 parent 0324c70
commit 4dd8e37
Showing 1 changed file with 6 additions and 6 deletions.
diff --git 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": "<db>",
         "collection": "<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.