The mc table share create command creates a new Delta Sharing configuration on an MinIO AIStor cluster. A share configuration defines a named collection of tables that can be accessed by external consumers through Delta Sharing tokens. Example The following command creates a share named analytics-share with a Delta table on the myaistor MinIO AIStor cluster:

The mc support telemetry record command streams captured trace calls to a file. Use the --sample flag to modify the number of calls traced and adjust the impact on performance. In addition to creating a file with the telemetry data, the command outputs the number of packets saved, the file name and path, and instructions for uploading the generated file to SUBNET. You can replay a recorded file and stream the telemetry to an OpenTelemetry Protocol (OTLP)-compatible collector by HTTP interface with mc support telemetry replay. You can also analyze the recorded file locally with an interactive terminal interface using mc support telemetry analyze.

mc support profile runs a system profile for your deployment. The results of the profile can provide insight into the Object Store process running on a given node. The resulting report is intended for use by MinIO AIStor Engineering. You can upload the report to SUBNET. Independent or third-party use of these profiles for diagnostics and remediation is done at your own risk. Syntax Example This command retrieves the CPU profile on an MinIO AIStor deployment with the alias myaistor. The profile runs for the default of 10 seconds.

This page covers settings that control Delta Sharing behavior for the MinIO AIStor process. Delta Sharing enables external applications to access shared datasets using the open Delta Sharing protocol. 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.

Networking has the greatest impact on AIStor Server performance. Low per-host bandwidth artificially constrains the potential performance of the storage. MinIO recommends high speed networking to support the maximum possible throughput of the attached storage (aggregated drives, storage controllers, and PCIe busses). For best performance, use 100GbE or higher networking infrastructure. The following table provides a general guideline for the maximum storage throughput supported by a given physical or virtual network interface. This table assumes all network infrastructure components, such as routers, switches, and physical cabling, also supports the NIC bandwidth.

MinIO Java SDK is Simple Storage Service (aka S3) client to perform bucket and object operations to any Amazon S3 compatible object storage service. For a complete list of APIs and examples, please take a look at the Java Client API Reference documentation. Minimum requirements Java 1.8 or above.

This page covers settings for connecting MinIO AIStor to an external etcd cluster. Etcd provides a distributed key-value store used for DNS-based bucket routing with virtual-host-style access. 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 MinIO Rust SDK is a Simple Storage Service (aka S3) client for performing bucket and object operations to any Amazon S3 compatible object storage service. It provides a strongly-typed, async-first interface to the MinIO and Amazon S3-compatible object storage APIs. Each supported S3 operation has a corresponding request builder (for example: [BucketExists], [PutObject], [UploadPartCopy]), which allows users to configure request parameters using a fluent builder pattern. All request builders implement the [S3Api] trait, which provides the async send method to execute the request and return a typed response.

You can configure MinIO AIStor behavior by setting environment variables using the ObjectStore custom resource. The Operator writes these variables to a configuration file accessible by all MinIO AIStor Pods in the object store. Overview Version changed Support for valueFrom with configMapKeyRef and secretKeyRef requires Operator version RELEASE.2025-10-16T16-46-38Z or later. The Operator supports two methods for setting environment variables:

Configure MinIO AIStor Operator behavior with environment variables. Includes TLS settings, namespace watching, Prometheus integration, and OpenTelemetry support.