The following section documents environment variables for configuring AIStor to publish audit logs to an HTTP webhook endpoint. See Publish Audit Logs to HTTP Webhook for more complete documentation and tutorials on using these environment variables. Example Environment Variables You can specify multiple webhook endpoints as audit log targets by appending a unique identifier _ID for each set of related logging settings.

This page covers settings that control root (superuser) access for the AIStor process. The root user has complete access and permissions to perform operations on the AIStor deployment. Root User and Root Password are required even if you use the MinIO Key Encryption Service or other key management utility. 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 environment variables for configuring AIStor to use drive-level cache for frequently accessed objects. When enabled, AIStor caches the metadata of accessed objects to node memory on PUT and GET requests. When the available memory reaches capacity, AIStor ejects the oldest last-accessed object from the cache. This keeps the most frequently accessed objects in the cache. Cache configuration settings control fundamental AIStor behavior and functionality. Test configuration changes in a lower environment, such as DEV or QA, before applying to production. Enable Environment Variable MINIO_CACHE_ENABLE Configuration Setting There is no configuration setting for this variable, as these settings apply at server startup. Set to on to use the drive cache feature.

AIStor supports running in S3 Express Mode. This mode enables directory bucket behavior for optimized heirarchial storage structures. While object store prefixes generally support organized storage, S3 Express Mode implements the specific directory bucket behaviors documented by AWS. S3Express mode disables most API operations outside of simple bucket and object PUT, GET, DELETE, and LIST operations. All other API operations return not supported errors, including operations for versioning, locking, and replication.

The mc ls command lists buckets and objects on an AIStor deployment. You can also use mc ls to list objects on S3-compatible services. Syntax Example The following command lists all objects in a bucket on the myaistor deployment:

AIStor Server uses the built-in scanner to check objects for healing and to take any scheduled object actions. Such actions may include: calculate data usage on drives evaluate and apply configured lifecycle management or object retention rules perform bucket or site replication check objects for missing or corrupted data or parity shards and perform healing The scanner performs these functions at two levels: cluster and bucket. At the cluster level, the scanner splits all buckets into groups and scans one group of buckets at a time. The scanner starts with any new buckets added since the last scan, then randomizes the scanning of other buckets. The scanner completes checks on all bucket groups before starting over with a new set of scans.

The mc table namespace create command creates a new Iceberg namespace within a warehouse on an AIStor cluster. A namespace is an organizational unit within a warehouse that groups related tables. Namespaces can have custom properties for categorization and management. Example The following command creates a namespace named prod in the analytics warehouse on the myaistor AIStor cluster:

The AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). Batch jobs run directly on the AIStor deployment to take advantage of the server-side processing power without constraints of the local machine where you run the AIStor Client. The keyrotate batch job type performs the following operations on objects in an AIStor deployment: Encrypts plaintext (unencrypted) objects using SSE-KMS. Rotates encryption keys for objects already encrypted with SSE-S3 or SSE-KMS using SSE-KMS. Rotates encryption keys for internal AIStor subsystems (IAM configuration, server configuration, tier configuration, and bucket metadata). The YAML configuration supports filters to restrict key rotation to a specific set of objects by creation date, tags, metadata, KMS key, or encryption status. You can also define retry attempts or set a notification endpoint and token.

Use the mc support perf command to review the performance of the S3 API (read/write), network IO, and storage (drive read/write). The resulting tests can provide general guidance of deployment performance under S3 GET and PUT requests and identify any potential bottlenecks. For more complete performance testing, consider using a combination of load-testing using your staging application environments and the MinIO Warp S3 benchmarking tool. The command has the following syntax:

The mc legalhold info command returns the current legal hold setting for an object or objects. mc legalhold requires that the specified bucket has object locking enabled. You can enable object locking at bucket creation. See mc mb --with-lock for documentation on creating buckets with object locking enabled. Version changed Beginning with RELEASE.2025-05-20T20-30-00Z, AIStor allows setting object locking and retention rules on any existing bucket. Earlier versions of AIStor only allowed setting retention rules for buckets at the bucket’s creation.