Publish Events to NATS

Buckit supports publishing bucket notification events to a NATS service endpoint.

NATS Streaming Deprecated

NATS Streaming is deprecated. Migrate to JetStream instead.

The related Buckit configuration options and environment variables are deprecated.

Add a NATS Endpoint to a Buckit Deployment

The following procedure adds a new NATS service endpoint for supporting bucket notifications in a Buckit deployment.

Prerequisites

Buckit `bm` Command Line Tool

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

1) Add the NATS Endpoint to Buckit

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

Environment Variables

Buckit supports specifying the NATS service endpoint and associated configuration settings using environment variables. The buckit server process applies the specified settings on its next startup.

The following example code sets all environment variables related to configuring an NATS service endpoint. The minimum required variables are MINIO_NOTIFY_NATS_ADDRESS and MINIO_NOTIFY_NATS_SUBJECT:

   export MINIO_NOTIFY_NATS_ENABLE_<IDENTIFIER>="on"
   export MINIO_NOTIFY_NATS_ADDRESS_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_SUBJECT_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_USERNAME_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_PASSWORD_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_TOKEN_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_TLS_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_TLS_SKIP_VERIFY_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_PING_INTERVAL_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_QUEUE_DIR_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_QUEUE_LIMIT_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_CERT_AUTHORITY_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_CLIENT_CERT_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_CLIENT_KEY_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_COMMENT_<IDENTIFIER>="<string>"
   export MINIO_NOTIFY_NATS_JETSTREAM_<IDENTIFIER>="<string>"

Replace <IDENTIFIER> with a unique descriptive string for the NATS 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 NATS service endpoint on the Buckit deployment, the new settings override any existing settings for that endpoint. Use bm admin config get notify_nats to review the currently configured NATS endpoints on the Buckit deployment.
Replace <ENDPOINT> with the hostname and port of the NATS service endpoint. For example: nats-endpoint.example.com:4222

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

Configuration Settings

Buckit supports adding or updating NATS endpoints on a running buckit server process using the bm admin config set command and the notify_nats configuration key. You must restart the buckit server process to apply any new or updated configuration settings.

The following example code sets all settings related to configuring an NATS service endpoint. The minimum required setting are notify_nats address and notify_nats subject:

bm admin config set ALIAS/ notify_nats:IDENTIFIER \
   address="HOSTNAME" \
   subject="<string>" \
   username="<string>" \
   password="<string>" \
   token="<string>" \
   nats_jetstream="<string>" \
   tls="<string>" \
   tls_skip_verify="<string>" \
   ping_interval="<string>" \
   cert_authority="<string>" \
   client_cert="<string>" \
   client_key="<string>" \
   queue_dir="<string>" \
   queue_limit="<string>" \
   comment="<string>"

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

If the specified IDENTIFIER matches an existing NATS service endpoint on the Buckit deployment, the new settings override any existing settings for that endpoint. Use bm admin config get notify_nats to review the currently configured NATS endpoints on the Buckit deployment.
Replace ENDPOINT with the hostname and port of the NATS service endpoint. For example: nats-endpoint.example.com:4222.

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

1) Restart the Buckit Deployment

You must restart the Buckit deployment to apply the configuration changes. Use the bm admin service restart command to restart the deployment.

bm admin service restart ALIAS

Replace ALIAS with the alias of the deployment to restart.

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

SQS ARNs: arn:minio:sqs::primary:nats

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

Identifying the ARN for your bucket notifications

You defined the <IDENTIFIER> to assign to the target ARN for your bucket notifications when creating the endpoint previously. The steps below return the ARNs configured on the deployment. Identify the ARN created previously by looking for the <IDENTIFIER> you specified.

Review the JSON output

Copy and run the following command, replacing ALIAS with the alias of the deployment.
```
bm admin info --json ALIAS
```
In the JSON output, look for the key info.sqsARN.

The ARN you need is the value of that key that matches the <IDENTIFIER> you specified.

For example, arn:minio:sqs::primary:nats.

Use jq to parse the JSON for the value

Install jq
Copy and run the following command, replacing ALIAS with the alias of the deployment.
```
bm admin info --json ALIAS | jq  .info.sqsARN
```
This returns the ARN to use for notifications, such as arn:minio:sqs::primary:nats

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

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

bm event add ALIAS/BUCKET arn:minio:sqs::primary:nats \
  --event EVENTS

Replace ALIAS with the alias of a Buckit 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 Buckit triggers notifications.

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

bm event ls ALIAS/BUCKET arn:minio:sqs::primary:nats

4) Validate the Configured Events

Perform an action on the bucket for which you configured the new event and check the NATS 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 bm cp command to create a new object in the bucket and trigger a notification.

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

Update an NATS Endpoint in a Buckit Deployment

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

Prerequisites

Buckit `bm` Command Line Tool

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

1) List Configured NATS Endpoints In The Deployment

Use the bm admin config get command to list the currently configured NATS service endpoints in the deployment:

bm admin config get ALIAS/ notify_nats

Replace ALIAS with the alias of the Buckit deployment.

The command output resembles the following:

notify_nats:primary password="yoursecret" subject="" address="nats-endpoint.example.com:4222"  token="" username="yourusername" ping_interval="0" queue_limit="0" tls="off" tls_skip_verify="off" queue_dir="" streaming_enable="on" nats_jetstream="on"
notify_nats:secondary password="yoursecret" subject="" address="nats-endpoint.example.com:4222"  token="" username="yourusername" ping_interval="0" queue_limit="0" tls="off" tls_skip_verify="off" queue_dir="" streaming_enable="on" nats_jetstream="on"

The notify_nats key is the top-level configuration key for an NATS Notification Settings. The address key specifies the NATS service endpoint for the given notify_nats key. The notify_nats:<IDENTIFIER> suffix describes the unique identifier for that NATS service endpoint.

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

2) Update the NATS Endpoint

Use the bm admin config set command to set the new configuration for the NATS service endpoint:

bm admin config set ALIAS/ notify_nats:IDENTIFIER \
   address="HOSTNAME" \
   subject="<string>" \
   username="<string>" \
   password="<string>" \
   token="<string>" \
   tls="<string>" \
   tls_skip_verify="<string>" \
   ping_interval="<string>" \
   nats_jetstream="<string>" \
   cert_authority="<string>" \
   client_cert="<string>" \
   client_key="<string>" \
   queue_dir="<string>" \
   queue_limit="<string>" \
   comment="<string>"

The notify_nats address configuration setting is the minimum required for an NATS service endpoint. All other configuration settings are optional. See NATS Notification Settings for a complete list of NATS configuration settings.

3) Restart the Buckit Deployment

You must restart the Buckit deployment to apply the configuration changes. Use the bm admin service restart command to restart the deployment.

bm admin service restart ALIAS

Replace ALIAS with the alias of the deployment to restart.

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

SQS ARNs: arn:minio:sqs::primary:nats

4) Validate the Changes

Perform an action on a bucket which has an event configuration using the updated NATS service endpoint and check the NATS 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 bm cp command to create a new object in the bucket and trigger a notification.

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

Publish Events to NATS

Add a NATS Endpoint to a Buckit Deployment

Prerequisites

Buckit bm Command Line Tool

1) Add the NATS Endpoint to Buckit

1) Restart the Buckit Deployment

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

4) Validate the Configured Events

Update an NATS Endpoint in a Buckit Deployment

Prerequisites

Buckit bm Command Line Tool

1) List Configured NATS Endpoints In The Deployment

2) Update the NATS Endpoint

3) Restart the Buckit Deployment

4) Validate the Changes

Buckit `bm` Command Line Tool

Buckit `bm` Command Line Tool