This page documents all requirements of bucket replication configurations, including: Active-Passive Active-Active Data Resynchronization Ensure you meet the following prerequisites before you set up any of these replication configurations. Permissions required for setting up bucket replication Bucket replication requires specific permissions on the source and destination deployments to configure and enable replication rules.

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.

This section provides documentation and guidance for installing AIStor. Each subsection represents a supported platform, where guidance reflects the specific installation and configuration methods associated with that platform. If you need to install a key management service to manage cryptographic keys while objects are at rest, see the MinIO KMS docs. If you need to install DirectPV to manage container storage volumes in a Kubernetes environment, see the MinIO DirectPV docs.

This procedure deploys AIStor Object Store on Kubernetes clusters in an airgapped environment. An airgapped environment is a network environment that has no direct connection to external networks or the internet. Installing AIStor in an airgapped environment requires copying all required container images and Helm charts to private registries accessible within the airgapped network. Airgap deployment consists of two phases: External Preparation (requires internet access): Download Helm charts and copy container images to your private registries from a system with network access to both the internet and your private registries. Airgapped Deployment (within airgapped environment): Install AIStor using the mirrored resources from within your airgapped Kubernetes environment. This procedure assumes you or your organization have existing procedures and tooling for facilitating such copying. Defer to your organization’s procedures on importing data from the internet into the airgapped environment. You cannot complete the first phase without tooling to facilitate the download-and-copy steps.

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.

AIStor supports deploying resources onto Windows hosts for local development and evaluation. For the purposes of evaluation or local development, MinIO recommends using a machine released in the last 4 years with at least 8 GB of RAM. You can use any supported version of Windows. For testing or local development using a virtualized environment, including Windows Subsystem for Linux (WSL), use a machine with a higher number of cores and 16 or 32GB of RAM.

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 one or more Active Directory or LDAP (AD/LDAP) services for external management of user identities.

Install on Kubernetes Deploy AIStor on Kubernetes

AIStor supports compressing objects to reduce disk usage. Objects are compressed on PUT before writing to disk, and uncompressed on GET before they are sent to the client. This makes the compression process transparent to client applications and services. Depending on the type of data, compression may also increase overall throughput. Write throughput for a production deployment is generally 500MB per second or greater per available CPU core in the system. Decompression is approximately 1 GB per second or greater for each CPU core.

This procedure downloads and installs the AIStor Server onto a host running Microsoft Windows Server or Windows 11 Professional Edition. Review the Hardware and System Requirements to ensure your target infrastructure meets our guidance. Procedure Download the AIStor Server binary Invoke-WebRequest https://dl.min.io/aistor/minio/release/windows-amd64/minio -OutFile C:\minio.exe Create a data directory for use with the server The following example uses the path $HOME/minio/data. Changes this path to reflect the folder, storage volume, or drive intended for use with the server.