The following guides provide instructions for deploying AIStor onto Windows infrastructure.

Install on Kubernetes Deploy AIStor on Kubernetes

AIStor supports publishing bucket notification events to MQTT server/broker endpoint. Prerequisites MQTT 3.1 or 3.1.1 Server/Broker This procedure assumes an existing MQTT 3.1 or 3.1.1 server/broker to which the AIStor Server has connectivity. See the mqtt.org software listing for a list of MQTT-compatible server/brokers.

This page documents the steps necessary to add a new AIStor installation to an existing Site Replication configuration. The procedures assumes a new AIStor installations and an existing set of deployments configured for Site Replication. The existing configuration must have all AIStor peer sites reachable and healthy. If any of the sites are unreachable or permanently lost, you must first remove the unreachable site(s) with mc admin replicate rm before expanding with the new site.

You can use the AIStor Console to perform many of the deployment monitoring and management functions available in AIStor, such as: License to monitor the status and expiration of the MinIO Commercial License used for the AIStor deployment. Monitor the health and activity of the deployment by reviewing metrics, server or audit logs, trace history, S3 events, or drive health. Configure alerts by adding or managing a notification target. Set up site replication to synchronize datacenters for timely access across geographically dispersed workforces or for disaster preparedness. Configure deployment settings. Overview The Overview page displays summary information for a deployment including:

Each procedure on this page creates a new object lifecycle management rule that expires objects on an AIStor bucket. This procedure supports use cases like removing “old” objects after a certain time period or calendar date. Requirements Install and configure AIStor Client This procedure uses the AIStor Client (mc) for performing operations on the AIStor cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.

In rare circumstances, you may need to restore site replication service account information to a peer in the cluster. Seeing AccessDenied for site replication calls either in logs or with :mc-cmd:mc admin trace indicates a need to restore service account information to a peer. This error typically results when the service accounts for site replication of one of the peer sites have been lost or corrupted. Procedure To restore the required information, export the service account information from an existing healthy peer site and import it to the site with the missing account information.

AIStor bucket notifications allow administrators to send notifications to supported external services when a events occurs on either an object or bucket. AIStor server supports a range of possible events, listed below, that can trigger a notification. AIStor supports bucket and object-level S3 events similar to the Amazon S3 Event Notifications. Supported notification targets AIStor supports publishing event notifications to the following targets:

If you integrate AIStor with Active Directory (AD/LDAP) as your identity provider, you can also manage access with AD/LDAP. AIStor can map a user’s Distinguished Name or group Distinguished Names (DNs) to existing policies. See Active Directory/LDAP Identity Management for configuring the integration. This page explains how to create AIStor access policies that match the AD/LDAP DNs. AIStor supports configuring a single Active Directory or LDAP (AD/LDAP) service for external management of user identities. Enabling AD/LDAP external identity management disables the AIStor internal IDP.

You can enable versioning using one of the following: At bucket creation AIStor Console (WebUI) AIStor Client CLI Developers can also enable versioning on buckets through an S3-compatible SDK Enable versioning at bucket creation AIStor Console When creating a bucket in the Console, select either Versioned as the bucket Type.