Publish Events to Webhook

AIStor supports publishing bucket notification events to a webhook service endpoint.

Prerequisites

  • The AIStor mc command line tool

    This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions.

Add a webhook endpoint to an AIStor Server

The following procedure adds a new webhook service endpoint for supporting bucket notifications in an AIStor Server.

  1. Add the webhook endpoint to AIStor.

    You can configure a new webhook service endpoint using either environment variables or by setting runtime configuration settings.

    If you define both environment variables and configuration settings for the deployment, the settings defined by environment variables are used.
  2. Restart the AIStor Server.

    You must restart the AIStor Server to apply the configuration changes. Use the mc admin service restart command to restart the deployment.

    mc admin service restart ALIAS
    

    Replace ALIAS with the alias of the deployment to restart.

    The minio server process prints a line on startup for each configured webhook target similar to the following:

    SQS ARNs: arn:minio:sqs::primary:webhook
    

    You must specify the ARN resource when configuring bucket notifications with the associated webhook deployment as a target.

  3. Configure bucket notifications using the webhook endpoint as a target.

    Use the mc event add command to add a new bucket notification event with the configured webhook service as a target:

    mc event add ALIAS/BUCKET arn:minio:sqs::primary:webhook \
      --event EVENTS
    
    • Replace ALIAS with the alias of an AIStor Server.
    • Replace BUCKET with the name of the bucket in which to configure the event.
    • Replace EVENTS with a comma-separated list of events for which AIStor triggers notifications.

    Use mc event ls to view all configured bucket events for a given notification target:

    mc event ls ALIAS/BUCKET arn:minio:sqs::primary:webhook
    
  4. Validate the configured events.

    Perform an action on the bucket for which you configured the new event and check the webhook service for the notification data. The action required depends on which events were specified when configuring the bucket notification.

    For example, if the bucket notification configuration includes the s3:ObjectCreated:Put event, you can use the mc cp command to create a new object in the bucket and trigger a notification.

    mc cp ~/data/new-object.txt ALIAS/BUCKET
    

Update a webhook endpoint in an AIStor Server

The following procedure updates an existing webhook service endpoint for supporting bucket notifications in an AIStor Server.

  1. List configured webhook endpoints in the deployment.

    Use the mc admin config get command to list the currently configured webhook service endpoints in the deployment:

    mc admin config get ALIAS/ notify_webhook
    

    Replace ALIAS with the alias of the AIStor Server.

    The command output resembles the following:

    notify_webhook:primary endpoint="https://webhook.example.com" auth_token="" queue_limit="0" queue_dir="" client_cert="" client_key=""
    notify_webhook:secondary endpoint="https://webhook.example.com" auth_token="" queue_limit="0" queue_dir="" client_cert="" client_key=""
    

    Note the identifier for the webhook service endpoint you want to update for the next step.

  2. Update the webhook endpoint.

    Use the mc admin config set command to set the new configuration for the webhook service endpoint:

    mc admin config set ALIAS/ notify_webhook:IDENTIFIER \
       endpoint="<ENDPOINT>" \
       auth_token="<string>" \
       queue_dir="<string>" \
       queue_limit="<string>" \
       client_cert="<string>" \
       client_key="<string>" \
       comment="<string>"
    
    • The notify_webhook endpoint configuration setting is the minimum required for a webhook service endpoint.
    • All other configuration settings are optional.

    See Webhook Service Notification Settings for a complete list of webhook configuration settings.

  3. Restart the AIStor Server.

    You must restart the AIStor Server to apply the configuration changes. Use the mc admin service restart command to restart the deployment.

    mc admin service restart ALIAS
    

    Replace ALIAS with the alias of the deployment to restart.

    The minio server process prints a line on startup for each configured webhook target similar to the following:

    SQS ARNs: arn:minio:sqs::primary:webhook
    
  4. Validate the changes.

    Perform an action on a bucket which has an event configuration using the updated webhook service endpoint and check the webhook service for the notification data. The action required depends on which events were specified when configuring the bucket notification.

    For example, if the bucket notification configuration includes the s3:ObjectCreated:Put event, you can use the mc cp command to create a new object in the bucket and trigger a notification.

    mc cp ~/data/new-object.txt ALIAS/BUCKET
    
All rights reserved 2024-Present, MinIO, Inc.