AIStor Object Locking (“Object Retention”) enforces Write-Once Read-Many (WORM) immutability to protect versioned objects from deletion. AIStor supports both duration based object retention and indefinite legal hold retention. AIStor Object Locking provides key data retention compliance and meets SEC17a-4(f), FINRA 4511(C), and CFTC 1.31(c)-(d) requirements as per Cohasset Associates. Overview

AIStor Server includes three groups of environment variables to manage how the server interacts with MinIO KMS, Key Encryption Service (KES), or static key files. You may only define one of the three sets, where defining more that one group results in errors and failure to start. Each configuration setting controls fundamental AIStor behavior and functionality. Test configuration changes in a lower environment, such as DEV or QA, before applying to production. Define any one set of these environment variables in the host system prior to starting or restarting the AIStor process. Refer to your operating system’s documentation for how to define an environment variable.

This page covers settings that configure the Erasure Code parity to use for objects written to the AIStor cluster. This impacts how AIStor uses the space on the drive(s) and how AIStor can recover objects stored on lost drives or similar issues. 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 covers deprecated settings that control core behavior of the AIStor Server process. Settings on this page may be removed at any time. Users should migrate to the recommended replacement at the earliest opportunity. 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 Server uses the environment variable value.

MinIO C++ SDK is Simple Storage Service (aka S3) client to perform bucket and object operations to any Amazon S3 compatible object storage service. For a complete list of APIs and examples, please take a look at the MinIO C++ Client API Reference Build requirements cmake 3.10 or higher. vcpkg package manager. A working C++ compiler that supports at least C++17. Installation via vcpkg MinIO C++ client SDK can be installed via vcpkg package manager:

Reference documentation for the AIStor Operator on Kubernetes. Includes CRD specifications, Helm chart values, environment variables, and AdminJob configuration.

The mc admin heal command scans for objects that are damaged or corrupted and heals those objects. mc admin heal is resource intensive and typically not required as a manual process, even after drive failures or corruption events. As a part of normal operations, AIStor: automatically heals objects damaged by silent bit rot corruption, drive failure, or other issues on each POST or GET operation. performs periodic background object healing using the scanner. aggressively heals objects after drive replacement. Refer to Object Healing for more details on how AIStor heals objects.

The mc event add command adds event notification triggers to a bucket. AIStor automatically sends triggered events to the configured notification target. Syntax EXAMPLE The following command creates a new event notification trigger for all PUT and DELETE operations for the mydata bucket on the myaistor AIStor deployment:

Syntax Example The following command lists all anonymous links for the mydata bucket on the myaistor AIStor deployment: mc anonymous links myaistor/mydata Syntax The command has the following syntax:

You can use the AIStor Console to perform several of the bucket and object management and interaction functions available in AIStor. Depending on the permissions and IAM policies for the authenticated user, you can: Browse, upload, revert, manage, and interact with objects. Browse, create, and manage buckets. Create or monitor remote tiers for object transition rules. Object browser The Object Browser lists the buckets and objects the authenticated user has access to on the deployment.