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.

MinIO AIStor supports publishing bucket notification events to a Redis service endpoint. Prerequisites The MinIO AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add a Redis endpoint to an AIStor Server The following procedure adds a new Redis service endpoint for supporting bucket notifications in an AIStor Server.

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

MinIO AIStor Tables uses standard MinIO AIStor policy-based access control (PBAC) to define authorized actions on warehouses, namespaces, tables, and views. For more information about PBAC in MinIO AIStor, see Access Control with Policy Management MinIO AIStor Tables policies use the s3tables: action namespace and the arn:aws:s3tables::: ARN scheme. Because MinIO AIStor uses Warehouse terminology where AWS S3 Tables uses TableBucket, the warehouse-level action names support both spellings as equivalent aliases. For example, s3tables:CreateWarehouse and s3tables:CreateTableBucket are interchangeable.

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.

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.

MinIO AIStor supports publishing bucket notification events to a AMQP 0-9-1 service endpoint such as RabbitMQ. Prerequisites AMQP 0-9-1 service endpoint. MinIO AIStor relies on the https://github.com/streadway/amqp project for AMQP connectivity. The project is primarily tested against RabbitMQ deployments, though other AMQP 0-9-1-compatible services may also work. This procedure assumes a RabbitMQ deployment using the 0-9-1 protocol as the service endpoint.

This page describes the end-to-end workflow for sharing a MinIO AIStor table with Databricks using the open Delta Sharing protocol. On the AIStor side, you create a share, generate an access token, and download a profile.share profile file. On the Databricks side, you create a provider from that profile and a catalog from the shared data, then query the table. This procedure assumes you have an existing Delta or Iceberg (UniForm) table in a MinIO AIStor bucket. If you do not, follow the Quickstart to create one first.

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.

This page provides an overview of AIStor Server deployment architectures from a production perspective. A production AIStor Server deployment consists of at least 4 hosts with homogeneous storage and compute resources. Each AIStor Server host in this pool has matching compute, storage, and network configurations These hosts make up a server pool, where the AIStor Server presents the aggregated compute, memory, and storage as a single resource to clients. Each pool consists of one or more erasure sets.