The mc support perf client command measures the network throughput from the local device running the AIStor Client to the server. The command displays results in a terminal user interface (TUI) with a spinner during testing and a tabular output showing TX (transmit) statistics for each server. Use this command to identify potential network performance bottlenecks between the client and server. Syntax Example The following command tests the network throughput from the local device to the server with alias myaistor.

The mc qos rule import command imports a Quality of Service (QoS) configuration to an AIStor deployment from a YAML file. The command reads the YAML configuration from standard input (STDIN). For more information, see Bucket-level Quality of Service. Syntax Example The following command imports the QoS configuration from a file named qos.yaml to the mybucket bucket on the myaistor deployment:

Generates a metrics scraping configuration file for use with Prometheus. Syntax Example The following command generates a v3 Prometheus scraping configuration file for the deployment at alias myaistor:

Description The mc idp ldap policy commands show the mapping relationships between policies and the associated groups or users. This command has the following subcommands: Subcommand Description attach Attaches one or more policies to an entity. detach Detaches one or more policies from an entity. entities Displays a list of mappings for a user, group, and/or policy.

The mc idp ldap accesskey ls displays a list of LDAP access key pairs. mc idp ldap accesskey ls is also known as mc idp ldap accesskey list. This command works against access keys created by an AD/LDAP user after authenticating to AIStor. Create AD/LDAP service accounts with the mc idp ldap accesskey create command. Authenticated users can manage their own long-term Access Keys using the AIStor Console. AIStor supports using AssumeRoleWithLDAPIdentity to generate temporary access keys using the Security Token Service.

The mc idp openid accesskey commands allow you to list, delete, or display information about OIDC access key pairs on the AIStor deployment. This command works against access keys created by an OIDC user after authenticating to AIStor. Authenticated users can create access keys with the AIStor console, with the mc admin accesskey create command, or with the mc idp openid accesskey create-with-login command. An authenticated user cannot create access keys for another OIDC user.

The mc get command retrieves objects from an AIStor deployment or S3-compatible service to a local filesystem. mc get provides a simplified interface for downloading files compared to mc cp or mc mirror. mc get uses a one-way download function that trades efficiency for the power and complexity of the other commands. Syntax Example The following command downloads an object from the myaistor deployment to the local filesystem:

The mc idp ldap accesskey info outputs information about the specified access key(s). This command works against access keys created by an AD/LDAP user after authenticating to AIStor. Create AD/LDAP service accounts with the mc idp ldap accesskey create command. Authenticated users can manage their own long-term Access Keys using the AIStor Console. AIStor supports using AssumeRoleWithLDAPIdentity to generate temporary access keys using the Security Token Service. Syntax Example The following example outputs details for the access key mykey from the myaistor deployment:

The mc event rm command removes an event notification trigger from a bucket. The mc event remove command has equivalent functionality to mc event rm. Syntax Example The following command removes a configured event notifications for the specified bucket notification target for the mydata bucket on the myaistor AIStor deployment:

This page provides guidance for upgrading AIStor Helm deployments on Kubernetes infrastructure. Overview AIStor Helm installations consist of two primary components: Operator Chart - Controls resources like CustomResourceDefinitions and core operator functionality Object Store Chart - Deploys and manages AIStor Object Store instances Upgrades involve updating these charts and deploying new container images. The exact procedure depends on your deployment environment’s network configuration and registry access.