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.

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.

mc support profile runs a system profile for your deployment. The results of the profile can provide insight into the Object Store process running on a given node. The resulting report is intended for use by AIStor Engineering. You can upload the report to SUBNET. Independent or third-party use of these profiles for diagnostics and remediation is done at your own risk. Syntax Example This command retrieves the CPU profile on an AIStor deployment with the alias myaistor. The profile runs for the default of 10 seconds.

Use the mc support proxy command to configure a proxy to use to communicate with MinIO SUBNET. Syntax Mc support proxy set Create a proxy URL for the AIStor deployment to use when communicating with MinIO SUBNET.

The mc support callhome command allows the enabling or disabling of sending diagnostic reports from a deployment to SUBNET. With Call Home, AIStor automatically sends a deployment’s diagnostic information to SUBNET. This makes it easier and quicker for the AIStor team to respond to questions and issues. AIStor enables this functionality by default for registered clusters. If you prefer not to automatically send these reports to SUBNET, you may disable callhome.

The mc support top disk command displays current drive statistics. Syntax Example The following command displays the current disk usage and performance on the alias myaistor.

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:

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 replicate backlog shows a list of unreplicated new or deleted objects. You can list the replication status of objects for a particular remote target. To do so, you must have the ARN of the remote target. You can mc replicate ls and mc replicate status to retrieve the remote targets configured for a bucket and find the ARN. Syntax Example The following command shows new or deleted objects in the notes bucket of the teamorange/projects prefix on the myaistor alias that have not yet replicated to a specific remote target bucket. The remote target’s ARN is arn:minio:replication::3bb8c736-4014-42c5-b3cb-d64e3ebaa75e:notes.