Bucket Notifications
MinIO bucket notifications allow administrators to send notifications to supported external services on certain object or bucket events. MinIO supports bucket and object-level S3 events similar to the Amazon S3 Event Notifications.
Supported Notification Targets
MinIO supports publishing event notifications to the following targets:
Target |
Description |
---|---|
AMQP (RabbitMQ) |
Publish notifications to an AMQP service such as RabbitMQ. See Publish Events to AMQP (RabbitMQ) for a tutorial. |
MQTT |
Publish notifications to an MQTT service. See Publish Events to MQTT for a tutorial. |
NATS |
Publish notifications to a NATS service. See Publish Events to NATS for a tutorial. |
NSQ |
Publish notifications to a NSQ service. See Publish Events to NSQ for a tutorial |
Elasticsearch |
Publish notifications to a Elasticsearch service. See Publish Events to Elasticsearch for a tutorial. |
Kafka |
Publish notifications to a Kafka service. See Publish Events to Kafka for a tutorial. |
MySQL |
Publish notifications to a MySQL service. See Publish Events to MySQL for a tutorial. |
PostgreSQL |
Publish notifications to a PostgreSQL service. See Publish Events to PostgreSQL for a tutorial. |
Redis |
Publish notifications to a Redis service. See Publish Events to Redis for a tutorial. |
webhook |
Publish notifications to a Webhook service. See Publish Events to Webhook for a tutorial. |
Asynchronous vs Synchronous Bucket Notifications
New in version RELEASE.2023-06-23T20-26-00Z: MinIO supports either asynchronous (default) or synchronous bucket notifications for all remote targets.
With asynchronous delivery, MinIO fires the event at the configured remote and does not wait for a response before continuing to the next event. Asynchronous bucket notification prioritizes sending events with the risk of some events being lost if the remote target has a transient issue during transit or processing.
With synchronous delivery, MinIO fires the event at the configured remote and then waits for the remote to confirm a successful receipt before continuing to the next event. Synchronous bucket notification prioritizes delivery of events with the risk of a slower event-send rate and queue fill.
To enable synchronous bucket notifications for all configured remote targets, use either of the following settings:
Set the
MINIO_API_SYNC_EVENTS
environment variable toon
and restart the MinIO deployment.Set the
api.sync_events
configuration setting toon
and restart the MinIO deployment.
Note
For synchronous and asynchronous events, MinIO maintains a per-remote queue where it stores unsent and pending events.
The queue limit defaults to 100000
.
MinIO discards new events when the queue is full.
You can increase the queue size as necessary to better accommodate the rate of event send and processing of the MinIO deployment and remote target.
Use the QUEUE_LIMIT
environment variable or configuration setting for your notification method to modify this limit.
For asynchronous events, MinIO allows a maximum of 50000
concurrent send
calls.
Supported S3 Event Types
MinIO bucket notifications are compatible with Amazon S3 Event Notifications. This section lists all supported events.
Object Events
MinIO supports triggering notifications on the following S3 object events:
Specify the wildcard *
character to select all events related to a prefix:
Replication Events
MinIO supports triggering notifications on the following S3 replication events:
Specify the wildcard *
character to select all s3:Replication
events:
ILM Transition Events
MinIO supports triggering notifications on the following S3 ILM transition events:
Specify the wildcard *
character to select all events related to a prefix:
Scanner Events
MinIO supports triggering notifications on the following S3 scanner transition events:
- s3:Scanner:ManyVersions
Scanner finds objects with more than 1,000 versions.
- s3:Scanner:BigPrefix
Scanner finds prefixes with more than 50,000 sub-folders.
Global Events
MinIO supports triggering notifications on the following global events. You can only listen to these events through the ListenNotification API: