This section provides guidance around recommended hardware configurations in production AIStor Server deployments. Hardware recommendations The recommendations below reflect our experience with assisting enterprise customers in deploying on a variety of IT infrastructures while maintaining the desired SLA/SLO. Use the recommended configurations below as a guideline for the physical or virtual hosts 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.

The pages in this section document settings for configuring AIStor to work with identity and access management (IAM) solutions. There is a page of settings for each of the IAM methods AIStor supports. Active Directory / LDAP OpenID Connect Security Token Service (STS) MinIO Identity Management Plugin MinIO Access Management Plugin

The mc idp ldap policy detach command detaches one or more polices from an entity. Syntax Example The following example detaches the policy userpolicy from the user bobfisher on the myaistor deployment.

mc inventory delete deletes an existing inventory configuration from a bucket. For running jobs, AIStor stops the job within approximately 10 seconds of deletion. This command has the following aliases: mc inventory remove mc inventory rm mc inventory del Deleting an inventory configuration immediately and permanently removes all associated data, including it’s YAML definition, stored metadata, and scheduling information for the job. It does not remove nor affect previously generated output files or partially generated files from deleting a job mid-run.

The mc qos status command displays QoS metrics and status for a specified bucket. Added in RELEASE.2025-12-20T04-58-37Z mc qos status requires AIStor Client RELEASE.2025-12-19T20-11-44Z or later and AIStor Server RELEASE.2025-12-20T04-58-37Z or later. The command displays a table that provides the following QoS metrics:

The mc ready command checks the status of a cluster and whether the cluster has read and write quorum. Example The following sends a GET request to the cluster at alias myaistor and returns its status. mc ready myaistor The command sends a GET request to the deployment at the alias myaistor.’ The command repeats the request until it is successful.

The mc support perf object command measures the S3 performance of reading and writing objects in a cluster. AIStor autotunes concurrency to obtain maximum throughput and IOPS (Input/Output Per Second). The command displays results in a terminal user interface (TUI) with a spinner during testing and a tabular output showing per-server PUT and GET performance statistics. Use this command to identify potential S3 API performance bottlenecks in your deployment. Syntax Example The following command measures the performance of S3 read/write of an object on the alias myaistor.

The mc replicate resync-backlog command triggers replication for backlogged objects by performing HeadObject operations on each unreplicated version. Use this command when replication is stuck or when you need to manually trigger replication for objects with PENDING or FAILED replication status. Syntax Example The following command triggers replication for all backlogged objects in the mybucket bucket on the myaistor alias:

The mc retention info command configures the Write-Once Read-Many (WORM) locking settings for an object or object(s) in a bucket. You can also set the default object lock settings for a bucket, where all objects without explicit object lock settings inherit the bucket default. To lock an object under legal hold, use mc legalhold set. mc retention info 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.

The mc sql command provides an S3 Select interface for performing sql queries on objects in the specified AIStor deployment. See Selecting content from objects for more information on S3 Select behavior and limitations. Syntax Example The following command queries all objects in the mydata bucket on the myaistor AIStor deployment: