Product
Hybrid Cloud Object Storage Hybrid Cloud Object Storage
Overview Architecture
Baremetal Baremetal
Overview Architecture
Erasure Code Calculator Erasure Code Calculator Reference Hardware Reference Hardware
Features
Active Active Replication Identity & Access Management Encryption Bucket & Object Immutability Bucket & Object Versioning Data Life Cycle Management & Tiering Automated Data Management Interfaces Monitoring Scalability
Native Versions
MinIO for VMware Tanzu MinIO for OpenShift MinIO for Amazon Elastic Kubernetes Service MinIO for Azure Kubernetes Service MinIO for Google Kubernetes Engine
Docs
MinIO Baremetal MinIO Object Storage for Baremetal Infrastructure MinIO Hybrid Cloud MinIO Object Storage for Kubernetes-Managed Private and Public Cloud Infrastructure MinIO for VMware Cloud Foundation MinIO Object Storage for VMware Cloud Foundation 4.2 MinIO Legacy Documentation Legacy Documentation for MinIO Object Storage
Solutions
VMware Discover how MinIO integrates with VMware across the portfolio from the Persistent Data platform to TKGI and how we support their Kubernetes ambitions. Splunk Find out how MinIO is delivering performance at scale for Splunk SmartStores Veeam Learn how MinIO and Veeam have partnered to drive performance and scalability for a variety of backup use cases. Azure to AWS S3 Gateway Learn how MinIO allows Azure Blob to speak Amazon’s S3 API HDFS Migration Modernize and simplify your big data storage infrastructure with high-performance, Kubernetes-native object storage from MinIO. Teradata Discover why MinIO is the Native Object Store (NOS) of choice for at-scale Teradata deployments Integrations Browse our vast portfolio of integrations
Resources Blog Pricing Download

Welcome to the upcoming version of the MinIO Documentation! The content on this page is under active development and may change at any time. If you can't find what you're looking for, check our legacy documentation. Thank you for your patience.

Publish Events to Redis

MinIO supports publishing bucket notification events to a Redis service endpoint.

Add a Redis Endpoint to a MinIO Deployment

The following procedure adds a new Redis service endpoint for supporting bucket notifications in a MinIO deployment.

Important

This procedure requires restarting all minio server processes associated to the deployment at the same time. There is typically a brief period of time during which API operations are interrupted or may fail.

Applications using an S3-compatible SDK with built-in retry logic or which implement manual retry logic typically experience no notable interruption in services. For applications which cannot use retry-logic, consider scheduling a maintenance period to minimize interruption of services while performing this procedure.

Prerequisites

MinIO mc Command Line Tool

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

1) Add the Redis Endpoint to MinIO

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

MinIO supports specifying the Redis service endpoint and associated configuration settings using environment variables. The minio server process applies the specified settings on its next startup.

The following example code sets all environment variables related to configuring an Redis service endpoint. The minimum required variables are:

set MINIO_NOTIFY_REDIS_ENABLE_<IDENTIFIER>="on"
set MINIO_NOTIFY_REDIS_ADDRESS_<IDENTIFIER>="<ENDPOINT>"
set MINIO_NOTIFY_REDIS_KEY_<IDENTIFIER>="<STRING>"
set MINIO_NOTIFY_REDIS_FORMAT_<IDENTIFIER>="<string>"
set MINIO_NOTIFY_REDIS_PASSWORD_<IDENTIFIER>="<string>"
set MINIO_NOTIFY_REDIS_QUEUE_DIR_<IDENTIFIER>="<string>"
set MINIO_NOTIFY_REDIS_QUEUE_LIMIT_<IDENTIFIER>="<string>"
set MINIO_NOTIFY_REDIS_COMMENT_<IDENTIFIER>="<string>"

  • Replace <IDENTIFIER> with a unique descriptive string for the TARGET service endpoint. Use the same <IDENTIFIER> value for all environment variables related to the new target service endpoint. The following examples assume an identifier of PRIMARY.

    If the specified <IDENTIFIER> matches an existing Redis service endpoint on the MinIO deployment, the new settings override any existing settings for that endpoint. Use mc admin config get notify_redis to review the currently configured Redis endpoints on the MinIO deployment.

  • Replace <ENDPOINT> with the URL of the Redis service endpoint. For example: https://redis.example.com:6369

See Redis Service for Bucket Notifications for complete documentation on each environment variable.

MinIO supports adding or updating Redis endpoints on a running minio server process using the mc admin config set command and the notify_redis configuration key. You must restart the minio server process to apply any new or updated configuration settings.

The following example code sets all settings related to configuring an Redis service endpoint. The minimum required settings are:

mc admin config set ALIAS/ notify_redis:IDENTIFIER \
  address="ENDPOINT" \
  key="<string>" \
  format="<string>" \
  password="<string>" \
  queue_dir="<string>" \
  queue_limit="<string>" \
  comment="<string>"

  • Replace IDENTIFIER with a unique descriptive string for the Redis service endpoint. The following examples in this procedure assume an identifier of PRIMARY.

    If the specified IDENTIFIER matches an existing Redis service endpoint on the MinIO deployment, the new settings override any existing settings for that endpoint. Use mc admin config get notify_redis to review the currently configured Redis endpoints on the MinIO deployment.

  • Replace ENDPOINT with the URL of the Redis service endpoint. For example: https://redis.example.com:6369

See Redis Bucket Notification Configuration Settings for complete documentation on each setting.

2) Restart the MinIO Deployment

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

Important

MinIO restarts all minio server processes associated to the deployment at the same time. Applications may experience a brief period of downtime during the restart process.

Consider scheduling the restart during a maintenance period to minimize interruption of services.

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 Redis target similar to the following:

SQS ARNs: arn:minio:sqs::primary:redis

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

3) Configure Bucket Notifications using the Redis Endpoint as a Target

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

mc event add ALIAS/BUCKET arn:minio:sqs::primary:redis \
  --event EVENTS

  • Replace ALIAS with the alias of a MinIO deployment.

  • 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 MinIO triggers notifications.

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

mc event list ALIAS/BUCKET arn:minio:sqs::primary:redis

4) Validate the Configured Events

Perform an action on the bucket for which you configured the new event and check the Redis 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 an Redis Endpoint in a MinIO Deployment

The following procedure updates an existing Redis service endpoint for supporting bucket notifications in a MinIO deployment.

Important

This procedure requires restarting all minio server processes associated to the deployment at the same time. There is typically a brief period of time during which API operations are interrupted or may fail.

Applications using an S3-compatible SDK with built-in retry logic or which implement manual retry logic typically experience no notable interruption in services. For applications which cannot use retry-logic, consider scheduling a maintenance period to minimize interruption of services while performing this procedure.

Prerequisites

MinIO mc Command Line Tool

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

1) List Configured Redis Endpoints In The Deployment

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

mc admin config get ALIAS/ notify_redis

Replace ALIAS with the alias of the MinIO deployment.

The command output resembles the following:

notify_redis:primary address="https://redis.example.com:6369" format="namespace" key="minioevent" password="" queue_dir="" queue_limit="0"
notify_redis:secondary address="https://redis.example.com:6369" format="namespace" key="minioevent" password="" queue_dir="" queue_limit="0"

The notify_redis key is the top-level configuration key for an Redis Service for Bucket Notifications. The address key specifies the Redis service endpoint for the given notify_redis key. The notify_redis:<IDENTIFIER> suffix describes the unique identifier for that Redis service endpoint.

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

2) Update the Redis Endpoint

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

mc admin config set ALIAS/ notify_redis:IDENTIFIER \
   address="ENDPOINT" \
   key="<string>" \
   format="<string>" \
   password="<string>" \
   queue_dir="<string>" \
   queue_limit="<string>" \
   comment="<string>"

The notify_redis address configuration setting is the minimum required for an Redis service endpoint. All other configuration settings are optional. See Redis Service for Bucket Notifications for a complete list of Redis configuration settings.

3) Restart the MinIO Deployment

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

Important

MinIO restarts all minio server processes associated to the deployment at the same time. Applications may experience a brief period of downtime during the restart process.

Consider scheduling the restart during a maintenance period to minimize interruption of services.

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 Redis target similar to the following:

SQS ARNs: arn:minio:sqs::primary:redis

3) Validate the Changes

Perform an action on a bucket which has an event configuration using the updated Redis service endpoint and check the Redis 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

This work is licensed under a Creative Commons Attribution 4.0 International License.

©2020-Present, MinIO, Inc.

Creative Commons License