MinIO AIStor supports publishing bucket notification events to a NATS service endpoint. Prerequisites The MinIO 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 NATS endpoint to an AIStor Server The following procedure adds a new NATS service endpoint for supporting bucket notifications in an AIStor Server.

This page documents the steps necessary to remove a peer site from existing Site Replication configuration. Remove the peer site using MinIO AIStor Console In a browser, access the Console for one of the existing replicated sites.

For identities managed by an external OpenID Connect (OIDC) compatible provider, MinIO AIStor can use either of two methods to assign policies to the authenticated user. MinIO AIStor by default denies access to all actions or resources not explicitly allowed by a user’s assigned or inherited policies. Authorization options with OIDC OIDC integration in MinIO AIStor supports either of the following authorization methods:

The procedure on this page creates a new bucket replication rule for one-way synchronization of objects from one MinIO AIStor bucket to another MinIO AIStor bucket. The buckets can be on the same MinIO AIStor deployment or on separate MinIO AIStor deployments. Requirements Replication requires all participating clusters meet the bucket replication requirements. This procedure assumes you have reviewed and validated those requirements.

The procedure on this page creates a new bucket replication rule for two-way “active-active” synchronization of objects between MinIO AIStor buckets. Requirements Replication requires all participating clusters meet the bucket replication requirements. This procedure assumes you have reviewed and validated those requirements.

You can use the MinIO AIStor Console to perform several of the identity and access management functions available in MinIO AIStor, such as: Create and manage user credentials or groups with the built-in MinIO AIStor IDP, connect to one or more OIDC providers, or add an LDAP provider for Single Sign On. Configure single sign on workflows using either OpenID Connect or AD/LDAP. View, manage, and create access policies. Create child access keys that inherit the parent’s permissions. IAM Users The IAM Users section provides a management interface for AIStor-managed users.

This page summarizes how a DELETE operation affects objects depending on the configuration of the bucket that contains the object. Any combination of the following factors may impact how DELETE operations function: Bucket versioning Object locking rules Object Lifecycle Management rules Object tiering Site or bucket replication Scanner Permissions MinIO AIStor uses a policy based access control system for access management. The user or service account must provide the correct policy action and conditions to allow a DELETE for the bucket and object.

AIStor Server supports publishing bucket notification events to an Elasticsearch service endpoint. Prerequisites Elasticsearch v7.0 or later. MinIO AIStor relies on the v7 project for Elastic connectivity. The elastic/v7 library specifically targets Elasticsearch v7.0 and is not compatible with earlier Elasticsearch versions.

MinIO AIStor supports publishing bucket notification events to NSQ service endpoint. Prerequisites The MinIO AIStor mc Command Line Tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add an NSQ endpoint to an AIStor Server The following procedure adds a new NSQ service endpoint for supporting bucket notifications in an AIStor Server.

The MinIO AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). The batch jobs run directly on the MinIO deployment to take advantage of the server-side processing power without constraints of the local machine where you run the MinIO Client. A batch file defines one job task. Once started, the MinIO AIStor server starts processing the batch job. Time to completion depends on the resources available to the deployment.