mc support telemetry analyze provides an interactive terminal interface for analyzing OpenTelemetry trace data. Use this command to perform quick latency analysis on recorded telemetry files. The command reads trace files created by mc support telemetry record and displays them in an interactive tree view with duration metrics, percentage breakdowns, and color-coded latency indicators. Syntax Example The following command opens an interactive analysis view for a local telemetry file:

This page documents settings for configuring an Kafka service as a target for Bucket Notifications. See Publish Events to Kafka 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, MinIO AIStor uses the environment variable value.

The mc table namespace remove command deletes an Iceberg namespace from a warehouse on an MinIO AIStor cluster. A namespace must be empty before it can be removed. Remove all tables and views in the namespace before deleting it. Example The following command removes the prod namespace from the analytics warehouse on the myaistor MinIO AIStor cluster:

The mc update command automatically updates the mc binary to the latest stable version. Running this command is equivalent to manually downloading the latest stable binary and using it to replace the existing mc installation on the host machine. Syntax Example The following command updates the mc binary on the local host:

The mc version commands enable, disable, and retrieve the versioning status for an MinIO AIStor bucket. For more information about object versioning in MinIO, see Bucket Versioning. mc version includes the following subcommands: Subcommand Description enable Enable versioning on the specified bucket. info Return the versioning status for the specified bucket. suspend Disable versioning on the specified bucket.

The mc table view create command creates a new Iceberg view on an MinIO AIStor cluster. Views are virtual tables defined by SQL queries. You can provide multiple SQL representations with different dialects for cross-engine compatibility. Example The following command creates a view named monthly_sales in the prod namespace of the analytics warehouse on the myaistor MinIO AIStor cluster:

This page documents settings for enabling external identity management using an Active Directory or LDAP service. See Configure MinIO AIStor for Authentication using Active Directory / LDAP for a tutorial on using these settings. MinIO AIStor supports configuring multiple LDAP providers. You provide a unique name for each provider configuration, allowing you to integrate with different directory services or organizational units within your environment. 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.

This page documents environment variables for configuring MinIO AIStor to publish data to an HTTP webhook endpoint and trigger an Object Lambda function. See Transforms with Object Lambda for more complete documentation and tutorials on using these environment variables. Environment Variables You can specify multiple targets by appending a unique identifier _ID for each set of related settings.

The pages in this section document settings for configuring MinIO AIStor to work with identity and access management (IAM) solutions. There is a page of settings for each of the IAM methods MinIO AIStor supports. Active Directory / LDAP OpenID Connect Security Token Service (STS) MinIO Identity Management Plugin MinIO Access Management Plugin

The MinIO AIStor Security Token Service (STS) AssumeRoleWithWebIdentity API endpoint generates temporary access credentials using a JSON Web Token (JWT) returned from a configured OIDC Identity Provider (IDP). This page documents the AIStor Server AssumeRoleWithWebIdentity endpoint. For instructions on implementing STS using an S3-compatible SDK, refer to the documentation for that SDK. The MinIO AIStor STS AssumeRoleWithWebIdentity API endpoint is modeled after the AWS AssumeRoleWithWebIdentity endpoint and shares certain request/response elements. This page documents the AIStor-specific syntax and links out to the AWS reference for all shared elements.