The mc table warehouse remove command removes an Iceberg warehouse from the catalog on an MinIO AIStor cluster. By default, this command removes only the warehouse registration from the catalog while preserving the underlying bucket and its contents. Use the --purge and --force flags together to also delete the underlying bucket and all its data. Example The following command removes the analytics warehouse from the myaistor MinIO AIStor cluster:

The MinIO AIStor Security Token Service (STS) APIs allow applications to generate temporary credentials for accessing the AIStor Server. The STS API is required for AIStor Servers configured to use external identity managers, as the API allows conversion of the external IDP credentials into AWS Signature v4-compatible credentials. STS API endpoints MinIO AIStor supports the following STS API endpoints:

The mc table warehouse command manages Iceberg warehouses on MinIO AIStor clusters. A warehouse is the top-level organizational unit in the Iceberg catalog hierarchy. Each warehouse maps to a bucket that stores table data and metadata. Subcommands mc table warehouse includes the following subcommands:

Version changed Beginning with AIStor Client RELEASE.2025-08-21T03-14-05Z, this command returns S3 call information gathered during the last minute. Previously, the command returned information about in-progress S3 API calls gathered from mc admin trace. The mc support top api command outputs the last minute of S3 API events on an MinIO AIStor server in real-time. The output is a high level summary of these calls. For more in-depth tracing, use mc admin trace.

This page covers settings that control behavior related to MinIO AIStor bucket notifications. 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 Python Client SDK provides high level APIs to access any MinIO Object Storage or other Amazon S3 compatible service. This Quickstart Guide covers how to install the MinIO client SDK, connect to the object storage service, and create a sample file uploader. The example below uses: Python version 3.7+ The MinIO mc command line tool The MinIO play test server The play server is a public MinIO cluster located at https://play.min.io. This cluster runs the latest stable version of MinIO and may be used for testing and development. The access credentials in the example are open to the public and all data uploaded to play should be considered public and world-readable.

This page covers settings for site identification and configuration. Each configuration setting controls fundamental MinIO AIStor behavior and functionality. Test configuration changes in a lower environment, such as DEV or QA, before applying to production. Site name Optional

The mc table share info command displays details of a Delta Sharing configuration on an MinIO AIStor cluster. Example The following command shows details of the analytics-share on the myaistor MinIO AIStor cluster: mc table share info myaistor/analytics-share Syntax The command has the following syntax:

The following page includes the full contents of the MinIO AIStor Custom Resource Definition V1 (Alpha) CustomResourceDefinition. API Reference Packages aistor.min.io/v1alpha1 aistor.min.io/v1alpha1 Package v1alpha1 is the v1alpha1 version of the Enterprise Operator API.

This page reflects limits and thresholds that apply to AIStor Server. Linux Kernel Requirements MinIO strongly recommends Linux kernel 6.8 or later for production deployments. See Linux Kernel Requirements for recommended distributions and performance details. S3 API practical limits Item Specification Maximum object size ~48 PiB (10,000 parts at 5 TiB each) Minimum object size 0 B Maximum object size per PUT operation 5 TiB for non-multipart upload~48 PiB for multipart upload Maximum versions per object 10,000; configurable with the MINIO_API_OBJECT_MAX_VERSIONS environment variable Bucket limits Item Specification Maximum number of buckets 500,000 (soft limit) Maximum length for bucket names 63 bytes Maximum length for each / separated segment of an object name 255 bytes Maximum objects per bucket no limit Reserved bucket and warehouse names The names minio and aistor are reserved for internal use and cannot be used as bucket names or AIStor Tables warehouse names. The reservation is an exact, case-sensitive match on the full name. Names that contain minio or aistor as a substring or prefix (for example, minio-backups or aistor-logs) are permitted.