AIStor supports deploying resources as a container for local development and evaluation. Performance The following table shows areas that have the greatest impact on AIStor performance, listed in order of importance. Prioritize securing the necessary components for each of these areas before focusing on other hardware resources, such as compute-related constraints.

Each procedure on this page creates a new object lifecycle management rule that expires objects on an AIStor bucket. This procedure supports use cases like removing “old” objects after a certain time period or calendar date. Requirements Install and configure AIStor Client This procedure uses the AIStor Client (mc) for performing operations on the AIStor cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.

This page documents settings for configuring an AMQP service as a target for Bucket Notifications. See Publish Events to AMQP (RabbitMQ) 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.

The mc support telemetry proxy command streams API events from all nodes on the AIStor deployment to the specified remote OpenTelemetry Protocol (OTLP)-compatible collector. Use the --sample flag to modify the number of calls traced and adjust the impact on performance. By default, the command runs in the current shell session until manually stopped. Syntax Example The following command streams the S3 API calls on the alias myaistor to an OTLP-compatible tracing service running on localhost.

This page documents settings for enabling external authorization management using the AIStor Access Management Plugin. See AIStor External Access 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.

Required release version This command is available in AIStor Client RELEASE.2025-03-31T22-38-30Z or later. The functionality requires AIStor RELEASE.2025-03-27T23-09-45Z or later. The mc admin accesskey sts-revoke command removes security token service (sts) credentials associated with an account. Revoke all STS tokens for an account, or specify the type(s) of STS tokens to revoke for an account.

The mc admin cluster bucket import command imports bucket metadata as created by the mc admin cluster bucket export command. You can use this command to manually restore the metadata to the specified bucket on an AIStor deployment. If you specify only the deployment as the target, this command applies the metadata objects to all matching buckets on the target. Syntax Example The following command imports bucket metadata for the myaistor deployment from a file:

Attaches one or more IAM policies to either an AIStor-managed user or a group. Exactly one --user or one --group is required. This command is intended for managing policy associations for MinIO-managed users only. For attaching policies to OpenID-managed users, see OpenID Connect Access Management.

Returns the specified policy in JSON format if it exists on the target AIStor deployment. Syntax Example The following command returns the policy readonly in JSON format from the deployment at alias myaistor.

Prints Prometheus metrics for a cluster. The output includes additional information about each metric, such as if its value is a counter or gauge. Syntax Example The following command prints v3 Prometheus metrics for the deployment at alias myaistor: