AIStor Key Manager supports installation on to Linux and Kubernetes infrastructures. Hardware and host configuration The following table lists the minimum requirements for a Key Manager server CPU Single-Socket Server-grade CPU with support for AES-NI instruction sets. Memory 8GiB available Storage 10GiB SSD or NVMe Network 10GbE low-latency interface Security standards typically discourage storing encryption keys on the same hosts as the encrypted data. As such, consider deploying Key Manager onto physical or virtual hosts that are fully separated or independent from the AIStor Object Store clusters they support.

This tutorial shows how to setup a KES server that uses Vault’s K/V engine as a persistent and secure key store: K E S C l i e n t K E S S e r v e r V a u l t Prerequisites To start a development server or interact with Vault using the Vault CLI, download the Vault binary.

AIStor automatically creates remote targets based on a given file path or resource location (such as an IP or DNS address). Users defining a remote target no longer need to determine an ARN for the remote bucket. The mc replicate add command creates a new server-side replication rule for a bucket on an AIStor deployment. The remote bucket must be on an AIStor deployment running the same version of AIStor as the local deployment.

The following page includes the full contents of the AIStor Server Helm Chart default values.yaml and all accompanying documentation. Removed fields The objectStore.features section (.spec.features in the CRD) has been fully removed in Operator RELEASE.2025-12-16T20-51-03Z. This section includes the following fields that previously provided shortcuts for common configurations.

The mc support top rpc command displays metrics for remote procedure calls (RPC). You can use key presses to change the sorting of the calls: r sorts by reconnections q sorts by out queue p sorts by ping Syntax Example The following command displays the current remote procedure call metrics for the alias myaistor deployment.

The mc support inspect command collects the data and metadata associated to objects at the specified path. If this information is required to diagnose a SUBNET issue, AIStor Engineering will provide the appropriate command. AIStor assembles this data from each backend drive storing an erasure shard for each specified object. For registered clusters, the file uploads to AIStor for use by the engineering team in support efforts. The command produces an encrypted zip file that includes all matching files with their respective host+drive+path. When writing the zip archive, AIStor also encrypts the zip index of file names included in the archive. The resulting report is intended for use by AIStor Engineering via SUBNET and may contain internal or private data points associated to the object. Exercise caution before sending a report to a third party or posting the report in a public forum.

The mc qos rule list command displays all configured Quality of Service (QoS) rules on an AIStor deployment. The command can also be invoked using the short name ls. For more information, see Bucket-level Quality of Service. Syntax Example The following command displays all QoS rules configured for the mybucket bucket on the myaistor deployment:

Version added RELEASE.2025-12-20T04-58-37Z Extended object naming mode requires AIStor RELEASE.2025-12-20T04-58-37Z or later. Extended object naming mode allows AIStor to encode object names to use characters that can be written to typical filesystems. The S3 specification allows for the use of all UTF-8 characters in object names. However, filesystems have their own restrictions on what is allowed to be written to disk.

This page covers settings that control behavior related to AIStor bucket notifications. 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 enabling external identity management using the MinIO Identity Management Plugin. See MinIO External Identity Management Plugin 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.