The AIStor Server process stores its configuration in the storage backend directory. These settings define runtime behavior of the AIStor Server process. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

This page documents settings for configuring an AMQP service as a target for Bucket Notifications. See Publish Events to AMQP (RabbitMQ) for a tutorial on using these settings. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

This section provides guidance around recommended hardware configurations in production AIStor Server deployments. Hardware Recommendations The following checklist follows our Recommended Configuration for each physical or virtual host supporting the AIStor Server deployment. Use the Erasure Code Calculator to provide baseline guidance for the number of hosts and drives necessary to meet your storage and availability requirements.

These sections contain reference material for deploying AIStor Server (minio) resources onto Baremetal infrastructure. AIStor Server uses a binary minio that is a drop-in replacement for the AGPLv3-licensed Community AIStor Server. The minio server command starts the Server process: minio server --license /path/to/minio.license /mnt/disk{1...4} See Installation and Management for a complete guide on installation. Syntax The AIStor Server minio process has a single command minio server.

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 three steps: Installing AIStor Setting up network encryption Setting up server-side encryption

AIStor supports deploying resources as a container for local development and evaluation. Performance The following table shows areas that have the greatest impact on AIStor performance, listed in order of importance. Prioritize securing the necessary components for each of these areas before focusing on other hardware resources, such as compute-related constraints.

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 Key Manager to manage cryptographic keys while objects are at rest, see the AIStor Key Manager docs. If you need to install Volume Manager to manage container storage volumes in a Kubernetes environment, see the AIStor Volume Manager docs.

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