This section provides documentation and guidance for installing MinIO 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.

Install on Kubernetes Deploy MinIO AIStor on Kubernetes

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

This procedure deploys MinIO AIStor 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 MinIO 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 MinIO 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.

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

MinIO 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.

You can exclude up to 10 prefixes on a bucket with versioning enabled. This is especially useful for Spark or Hadoop workloads or any process that initially creates objects with temporary prefixes. Prefixes A prefix is a common leading string of characters under a bucket that a set of objects share.

This page documents the steps necessary to add a new MinIO AIStor installation to an existing Site Replication configuration. The procedures assumes a new MinIO AIStor installations and an existing set of deployments configured for Site Replication. The existing configuration must have all MinIO 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.

Each procedure on this page creates a new object lifecycle management rule that expires objects on an MinIO 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 MinIO 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.

If you integrate MinIO AIStor with Active Directory (AD/LDAP) as your identity provider, you can also manage access with AD/LDAP. MinIO 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 MinIO AIStor access policies that match the AD/LDAP DNs. MinIO AIStor supports configuring one or more Active Directory or LDAP (AD/LDAP) services for external management of user identities.