MinIO AIStor is licensed under the MinIO Software License. An active license is required for production deployments. Install on Red Hat Enterprise Linux Deploy MinIO AIStor onto RHEL 10+

Configure load balancers and Ingress controllers for MinIO AIStor on Kubernetes. Includes examples for NGINX, HAProxy, and Traefik.

MinIO AIStor supports deploying resources onto Kubernetes infrastructure through our first-party operator model. MinIO AIStor also provides a Red Hat OpenShift certified operator. Setting up MinIO AIStor on Kubernetes 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) Kubernetes API support Production Kubernetes infrastructure should run currently supported releases of the Kubernetes API.

MinIO AIStor implements Transport Layer Security (TLS) 1.2+ encryption with support for Server Name Indication (SNI) for selecting relevant TLS certificates in response to client requests. MinIO AIStor supports two types of certificate management: Automatic TLS certificate provisioning (default) User-provided TLS certificates When deploying an MinIO AIStor resource, the CRD definition provides a certificates field for controlling certificate generation and behavior. This field is also available in the object store Helm chart.

Docs » Module code » h2o.model.model_base Source code for h2o.model.model_base # -*- encoding: utf-8 -*- import os im...

The procedure on this page creates a new object lifecycle management rule that transition objects from an MinIO AIStor bucket to a remote storage tier on the Google Cloud Storage (GCS) backend. This procedure supports use cases like moving aged data to low-cost public cloud storage solutions after a certain time period or calendar date. Requirements Install and configure mc This procedure uses 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.

MinIO AIStor is licensed under the MinIO Software License. An active license is required for production deployments. This section documents steps for installing and managing AIStor Server on macOS™ host machines. Procedure Install AIStor Server onto the macOS host The easiest way to install AIStor Server on macOS is using Homebrew.

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.

Docker Compose lets you define and run a multi-container application on a single host. You can use a Compose file to start several MinIO AIStor server instances in separate containers on the same machine, forming a distributed deployment behind an NGINX load balancer. This topology runs all server instances on a single host and is intended for development, testing, and staging environments only. It is not suitable for production. For production, deploy a distributed cluster across separate hosts. See Deploy MinIO AIStor as a Container for the single-node container procedure, or use a Kubernetes or Linux deployment for production. Prerequisites Familiarity with Docker Compose. Docker installed on your machine. A MinIO AIStor license file. MinIO AIStor requires a license to run. To request a free tier license, go to the MinIO AIStor pricing page and select Get Started under the Free tier. Save the license to minio.license in the same directory as the Compose file. For more information, see Licenses. Procedure Create the Compose file The following docker-compose.yaml starts four MinIO AIStor server instances, each with two named data volumes, and an NGINX service that reverse proxies and load balances across them. The shared command starts each server with the http://minio{1...4}/data{1...2} server pool definition.

This section provides documentation for administering MinIO AIStor deployments. Use this documentation to configure identity and access management, manage objects and buckets, set up replication, and configure the features that control how your deployment operates. MinIO AIStor requires authentication for every operation and uses policy-based access control to define authorized actions. Use MinIO AIStor’s Identity and Access Management (IAM) controls to manage who can access your deployment and what they can do, whether you use the built-in identity manager or integrate with external providers like OpenID Connect (OIDC) or Active Directory/LDAP.