NC | Backport to 5.18.2

docs/bucket-notifications.md

@@ -10,7 +10,7 @@ A notification json has these fields:
           If not specified, the notification is relevant for all events.
 - TopicArn: The connection file (see below). (To specify a Kafka target topic, see "Kafka Connection Fields" below).
 
-Example for a bucket's notification configuration, in a file:
+Example for a bucket's notification configuration on containerized environment, in a file:
 {
     "TopicConfigurations": [
         {
@@ -23,6 +23,18 @@ Example for a bucket's notification configuration, in a file:
     ]
 }
 
+Example for a bucket's notification configuration on Non-containerized environment, in a file:
+{
+    "TopicConfigurations": [
+        {
+	    "Id": "created_from_s3op",
+            "TopicArn": "secret-name/connect",
+            "Events": [
+                "s3:ObjectCreated:*"
+            ]
+        }
+    ]
+}
 
 ## Connection File
 A connection file contains some fields that specify the target notification server.

src/manage_nsfs/health.js

@@ -418,7 +418,7 @@ class NSFSHealth {
                 const connection_file_path = this.config_fs.get_connection_path_by_name(config_file_name);
                 const test_notif_err = await notifications_util.test_notifications([{
                     name: config_data.name,
-                    topic: [this.config_fs.json(config_file_name)]
+                    topic: [config_file_name]
                 }], this.config_fs.config_root);
                 if (test_notif_err) {
                     res = get_invalid_object(config_data.name, connection_file_path, undefined, test_notif_err.code);