Notification Service

The notification stack lets the Storage Service publish file events and lets clients consume them. It has two service adapters — the Event Aggregation Service (publishing) and the Event Consumer Service (consuming) — backed by RabbitMQ as the event broker.

To deploy and secure the notification services, follow the full deployment guide: Notification Services Configuration (which covers deployment plus authentication and permissions).

Use these guides to prepare your first deployment and operate existing installations:

• Event Aggregation Operations — preparation for first installations and upgrades, publishing limits, capacity, shutdown and validation.

• Event Consumer Operations — preparation for first installations and upgrades, capacity, ingress, graceful shutdown and validation.

• Event Consumer Dead-Letter Capture — bounded-redelivery and dead-letter capture for durable queues, and the operator dead-letter management runbook (browse, replay, discard).

For the notification API interface contracts and specifications, see API Specifications.