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.

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.

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.

Install on Kubernetes Deploy AIStor on Kubernetes

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.

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.

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.

AIStor supports deploying resources as a container for local development and evaluation. Setting up AIStor as a container involves these steps: Deploy AIStor as a container Set up network encryption (optional) Performance The following table shows areas that have the greatest impact on AIStor performance, listed in order of importance.

AIStor supports deploying resources onto Linux infrastructures and provides packages for Red Hat Enterprise Linux and Ubuntu Server platforms. Setting up AIStor on Linux involves these steps: Install AIStor Configure load balancing Set up network encryption Set up server-side encryption Enable FIPS mode (optional, for regulatory compliance)

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.