Configure plugin behavior

The plugin needs to know how to convert a bucket name into a base URI. The environment variable DSERVER_NOTIFY_BUCKET_TO_BASE_URI is used to specify that conversion, e.g.:

DSERVER_NOTIFY_BUCKET_TO_BASE_URI={"bucket": "ecs://bucket"}

It is also advisable to limit access to the notification listener to a certain IP range. Use:

DSERVER_NOTIFY_ALLOW_ACCESS_FROM=192.168.0.0/16

to specify the allowed remote network. To specify a single IP, use:

DSERVER_NOTIFY_ALLOW_ACCESS_FROM=192.168.1.1/32

Configure webhook in minio

The Publish Events to Webhook minio docs walks through the configuration for sending S3 event notifications to a webhook. Assuming a dserver with this plugin activated running at http://dserver:5000, and your minio instance with a bucket test-bucket at https://s3server:9000, use

# mc: minio client
mc config host add s3server http://s3server:9000 {admin_user} {admin_password}

# Note that the endpoint must be reachable when configuring, otherwise minio will reject
mc admin config set s3server/ notify_webhook:dtool  endpoint="http://dserver:5000/webhook/notify"
mc admin service restart s3server  # restart is necessary

# Activate the actual notifications
mc event add s3server/test-bucket arn:minio:sqs::testbucket:dtool --event "put,delete"

to configure a webhook endpoint identified by dtool and activate put and delete event notification. Choose the parameters for --event "put,delete" from minio’s Supported Bucket Evenets.

Note that minio is very strict on whom they talk to. If your dserver communicates via https, make sure that the server certificate uses SANs and that the signing authority’s root certificate is available to minio. See Install Certificates from Third-party CAs in the minio docs. Also assure all services are reachable by valid hostnames. Within a containerized environment such as launched with docker-compose , host names containing underscores _ may occur, but minio refuses to speak with such.

Configure webhook in NetApp StorageGRID

NetAPP StorageGRID is able to submit S3 event notifications when configured to communicate with an SNS endpoint, refer to the according sections of the NetApp StorageGRID docs for creating service endpoints and configuring event notifications.

In short, create an endpoint http://dserver:5000/webhook/notify with a suitable URN, i.e. urn:dserver:sns:region:notify:all, where you may pick all fields freely except urn and sns.

Next, enable event notifications for the desired bucket, i.e. for object creation events with a policy snippet like this:

<NotificationConfiguration>
  <TopicConfiguration>
    <Id>Object created</Id>
    <Topic>urn:dserver:sns:region:notify:all</Topic>
    <Event>s3:ObjectCreated:*</Event>
  </TopicConfiguration>
</NotificationConfiguration>