MinIO AIStor Object Locking (“Object Retention”) enforces Write-Once Read-Many (WORM) immutability to protect versioned objects from deletion. MinIO AIStor supports both duration based object retention and indefinite legal hold retention. MinIO AIStor Object Locking provides key data retention compliance and meets SEC17a-4(f), FINRA 4511(C), and CFTC 1.31(c)-(d) requirements as per Cohasset Associates. Overview

MinIO AIStor Tables uses standard MinIO AIStor policy-based access control (PBAC) to define authorized actions on warehouses, namespaces, and tables. For more information about PBAC in MinIO AIStor, see Access Control with Policy Management Resource reference ARN patterns MinIO AIStor Tables uses ARN patterns to identify resources in policies:

The MinIO AIStor Console is a rich graphical user interface that provides similar functionality to the mc command line tool. This page provides an overview of the MinIO AIStor Console and describes configuration options and instructions for logging in. Overview You can use the MinIO AIStor Console for administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.

MinIO AIStor brings the first native implementation of Delta Sharing to S3-compatible storage in private, public, and hybrid cloud environments.

This section provides documentation for operating and maintaining MinIO AIStor deployments. Use this documentation for Day 2 and ongoing operational tasks in production environments, including monitoring, scaling, troubleshooting, and managing production MinIO AIStor deployments. Performance and troubleshooting Optimize your deployment with performance tuning guidelines for CPU, memory, storage, and network. Validate your configuration with benchmarking tools. When issues arise, use the debugging and troubleshooting guide for HTTP tracing, diagnostics, and metadata inspection.

MinIO AIStor Tables implements native Iceberg tables support in MinIO AIStor object storage. This feature allows you to create, manage, and query Iceberg tables directly through MinIO AIStor with no dependencies on external catalog services or metadata databases. MinIO AIStor Tables is compatible with Iceberg Golang, the Iceberg V3 spec, and the Iceberg REST Catalog. Applications can interact with Iceberg entities through the MinIO AIStor Iceberg API while performing S3 operations through the object storage API.

Multi-tenancy allows multiple isolated workloads, teams, or customers to share a single MinIO AIStor deployment while maintaining data isolation and access control. IAM-based multi-tenancy The recommended approach uses a single deployment with IAM-based isolation. Each tenant is represented as an IAM user or group with policies that restrict access to specific buckets or prefixes.

Use the following examples to help design your own QoS rules. Basic rate limiting The following QoS rule sets a rate limit of 50 s3.PutObject requests per second with a burst of 10. The rule applies to all objects in the bucket and has the highest priority.

The MinIO AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). The batch jobs run directly on the MinIO AIStor deployment to take advantage of the server-side processing power without constraints of the local machine where you run the AIStor Client. The replicate batch job replicates objects from one MinIO AIStor deployment (the source deployment) to another MinIO AIStor deployment (the target deployment). The deployment specified as the alias becomes the ’local’ deployment for the purposes of replication.

Protect MinIO AIStor data directories from accidental deletion using kernel-level storage protection with SELinux or eBPF LSM.