The AIStor client mc support commands provides tools for analyzing deployment health or performance and for running diagnostics. You can also upload generated health reports for further analysis by AIStor engineering. mc support proxy set and mc support proxy remove are exceptions, as you may need to set up a proxy to complete the deployment registration. Subcommands mc support includes the following subcommands:

mc idp openid accesskey disable disables the specified access key on the AIStor deployment. Example and syntax Example The following example disables the access key mykey on the myaistor deployment:

The mc mb command creates a new bucket on an AIStor deployment. You can also use mc mb to create buckets on S3-compatible services. Syntax Example The following command creates a new bucket on the myaistor deployment:

Developers

Recommended hardware tests AIStor diagnostics Run the built in health diagnostic tool.

This page documents settings for enabling external identity management using an OpenID Connect (OIDC)-compatible provider. See OpenID Connect Access Management 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 watch command watches for events on the specified AIStor bucket or local filesystem path. For S3 services, use mc event add to configure bucket event notifications on S3-compatible services. You can also use mc watch against a local filesystem directory to produce similar results to running the inotify -e modify,create,delete,move command. Syntax Example The following command watches for events on any object or prefix in the mydata bucket on the myaistor AIStor deployment:

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

AIStor Server includes three groups of environment variables to manage how the server interacts with the AIStor Key Management Service (KMS), Key Encryption Service (KES), or static key files. You may only define one of the three sets, where defining more that one group results in errors and failure to start. Each configuration setting controls fundamental AIStor behavior and functionality. Test configuration changes in a lower environment, such as DEV or QA, before applying to production. Define any one set of these environment variables in the host system prior to starting or restarting the AIStor process. Refer to your operating system’s documentation for how to define an environment variable.

This page documents settings for enabling external identity management using an Active Directory or LDAP service. See Configure AIStor for Authentication using Active Directory / LDAP for a tutorial on using these settings. MinIO recommends using the mc idp ldap commands for LDAP management operations. These commands offer better validation and additional features, while providing the same settings as the identity_ldap configuration key. The identity_ldap configuration settings remains available for existing scripts and other tools.