Purpose
Push notifications to your own HTTPS endpoint when objects are created or removed —
the S3 event-notification model, aimed at integrations and automation. Every
delivery is signed so your receiver can prove it came from this Relayer.
When you use it
- Trigger a pipeline when a new object lands.
- Mirror delete events into an external index.
- Alert on lost objects (reduced-redundancy loss).
Controls
- Notification Rules list with a New rule button. Each rule row shows a short
rule id, the endpoint URL, its event-type chips, and the signing-key fingerprint.
Click a row to select it for editing. - New Rule / Edit Rule form:
- Endpoint URL — your receiver, such as an HTTPS webhook address.
- Event types (a checklist, one per line): object-created (all, plus Put, Post,
Copy), object-removed (all, plus Delete, DeleteMarkerCreated), and
reduced-redundancy lost object. - Create rule (new) or Save changes (edit), plus Cancel.
- Delete — shown only while editing an existing rule; asks for confirmation.
- Save this signing key dialog — appears once, immediately after you create a
rule. It shows the plain signing key a single time, with a Copy button, the key
fingerprint, and the algorithm. Copy it before closing; it can never be shown again. - Target Configuration panel — appears for a selected saved rule. It lists the
endpoint URL, the key fingerprint, the signature header, the timestamp header, the
signing algorithm, and the replay window, plus a collapsible payload-schema table
and an example event body. It also carries a Send test event button that
dispatches a test delivery to the endpoint. - Delivery history panel — a table of recent delivery attempts for the selected
rule: status (delivered / failed / pending, with a test badge on test events),
attempt count, last error, attempted-at and delivered-at times, plus a Refresh
button. Empty until the rule has fired or you send a test event.
Common tasks
- Notify on every upload: New rule → enter the endpoint URL → tick the
object-created (all) event → Create rule → copy the signing key from the one-time
dialog. - Verify a rule is reachable: select the rule → Send test event → check Delivery
history for a delivered (or failed) row. - Retire a rule: select it → Delete → confirm.
Gotchas
- The signing key is shown exactly once, at create time. If you lose it you must
recreate the rule — there is no re-reveal. - Selecting the broad (all) variant and a specific action of the same family both fire;
the UI does not stop you picking both. Pick the scope you actually want. - If webhook events are not enabled on this appliance the page reports that and the
list stays empty. - This is per-relayer object eventing. The separate audit webhook (streaming the full
audit trail to a SIEM) is configured in the install environment, not here.
Screenshots
