AIStor includes a Quality of Service (QoS) configuration that allows you to define rate limiting and concurrency controls for S3 requests on a per-bucket basis. This feature enables fine-grained control over API request rates and concurrent operations to ensure optimal resource utilization and prevent system overload. You can configure rules with QoS to do the following: Feature Description Rate Limiting Control the number of requests per second for specified operations Concurrency Control Limit the number of concurrent operations Prefix-based Targeting Apply limits to specific object prefixes within buckets API-specific Rules Target specific S3 operations Priority-based Evaluation Use rule priorities for complex scenarios In production environments, you typically write a YAML configuration file for your QoS rules that looks like the following:

This page covers settings for the AIStor Client mc. 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.

Description The mc batch commands allow you to run one or more job tasks on an AIStor deployment. Subcommands mc batch includes the following subcommands:

The mc batch list command outputs a list of the batch jobs currently in progress on a deployment. Syntax Example The following command outputs a list of all jobs currently in progress on the myaistor alias.

Syntax The mc admin decommission command starts the decommissioning process for an AIStor server pools. Decommissioning is designed for removing an older server pool whose hardware is no longer sufficient or performant compared to the pools in the deployment. AIStor automatically migrates data from the decommissioned pool to the remaining pools in the deployment based on the ratio of free space available in each pool. The process ignores unreadable objects, such as those that have lost read quorum, and continues with remaining objects in the pool.

The mc encrypt info command displays the default bucket encryption configuration. Syntax Example The following command displays the default encryption configuration for a bucket:

Description The mc event command supports adding, removing, and listing bucket event notifications. AIStor automatically sends triggered events to the configured notification targets. AIStor supports notification targets like AMQP (RabbitMQ), Redis, ElasticSearch, NATS and PostgreSQL. See Bucket Notifications for more information. Subcommands mc event includes the following subcommands:

mc batch status outputs the statuses of jobs currently running. Syntax Example The following command outputs the status of the specified job with JobID KwSysDpxcBU9FNhGkn2dCf currently in progress on the myaistor alias.

mc inventory migrate-from-batch converts an existing batch catalog YAML configuration (v2 format) to the inventory YAML format (v1 format). This command enables migration from the batch catalog system to the newer inventory system. The command transforms the YAML structure by: Changing apiVersion from v2 to v1. Removing the bucket field (the bucket is specified when submitting the configuration). Adding an id field with the specified inventory ID. Preserving all comments and other configuration fields. After converting the batch catalog YAML, use mc inventory put to upload the configuration to your target bucket.

The mc idp openid accesskey create-with-login command uses a browser-based login flow to authenticate with an OpenID Connect provider and generate access keys for use with AIStor. The command starts a local HTTP server, opens the OpenID authentication URL in your browser, and waits for the authentication callback. After successful authentication, it creates access keys using the policies associated with the authenticated OIDC user. For details, see the authentication flow section.