You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/bucket-notifications.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,14 @@ A notification json has these fields:
10
10
If not specified, the notification is relevant for all events.
11
11
- TopicArn: The connection file (see below). (To specify a Kafka target topic, see "Kafka Connection Fields" below).
12
12
13
+
Note that in alignment with AWS notification configuration, a test notification is sent to the external server during put-bucket-notification-configuration execution.
14
+
A successful test notification is a prequisite for the put-bucket-notification-configuration op.
15
+
13
16
Example for a bucket's notification configuration on containerized environment, in a file:
14
17
{
15
18
"TopicConfigurations": [
16
19
{
17
-
"Id": "created_from_s3op",
20
+
"Id": "created_from_s3op",
18
21
"TopicArn": "secret-name/connect.json",
19
22
"Events": [
20
23
"s3:ObjectCreated:*"
@@ -23,12 +26,12 @@ Example for a bucket's notification configuration on containerized environment,
23
26
]
24
27
}
25
28
26
-
Example for a bucket's notification configuration on Non-containerized environment, in a file:
29
+
Example for a bucket's notification configuration on a non-containerized environment, in a file:
0 commit comments