Managing Ceph Object Gateway notification destinations

Learn how notification destinations in IBM Storage Ceph Object Gateway define where S3 bucket event messages are delivered.

A notification destination represents an external endpoint that receives S3 bucket event messages. These destinations define how and where events are sent—for example to HTTPS endpoints, Kafka topics, AMQP queues, or custom services. Notification destinations are created once and can be reused across multiple bucket notifications.

Why notification destinations are important

Typical consumers include:
  • Stream processing services
  • Data ingestion pipelines
  • Automation tools
  • Audit and compliance systems
  • Analytics applications

Key components of a notification destination

A notification destination includes the following components:

Destination name
A unique identifier
Endpoint type
HTTPS, Kafka, AMQP, or other supported mechanisms
Endpoint details
URL, port, credentials, TLS settings, timeout, and retry configuration
Delivery format
How event data is packaged and transmitted
Associations
Bucket notifications that reference the destination

How notification destinations fit into the event architecture

The following sequence explains how destinations participate in event routing:
  1. The administrator creates one or more notification destinations.
  2. Bucket notifications reference these destinations.
  3. The Object Gateway monitors bucket events.
  4. When an event occurs, the gateway identifies the mapped destination.
  5. The event is delivered to the configured endpoint.

Use cases

Notification destinations support scenarios such as:
  • Sending new-object events to Kafka
  • Triggering workflows through HTTPS webhooks
  • Forwarding delete events to audit systems
  • Integrating with AMQP or message queues
  • Driving real-time data ingestion