Cross-Origin Resource Sharing (CORS) controls which web origins can access your MinIO AIStor resources. MinIO AIStor supports both global and per-bucket CORS configuration. Global CORS settings Configure global CORS behavior using the MINIO_API_CORS_ALLOW_ORIGIN environment variable or the api cors_allow_origin configuration setting.

MinIO AIStor supports publishing bucket notification events to a MySQL service endpoint. MinIO AIStor supports MySQL 5.7.8 and later only. Prerequisites MySQL 5.7.8 and later MinIO AIStor relies on features introduced with MySQL 5.7.8. 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.

This page documents the steps necessary to add a new MinIO AIStor installation to an existing Site Replication configuration. The procedures assumes a new MinIO AIStor installations and an existing set of deployments configured for Site Replication. The existing configuration must have all MinIO AIStor peer sites reachable and healthy. If any of the sites are unreachable or permanently lost, you must first remove the unreachable site(s) with mc admin replicate rm before expanding with the new site.

This guide covers a layered approach to performance validation for MinIO AIStor deployments using purpose-built tools. Run these tests before and after upgrades to establish baselines and detect regressions. For built-in MinIO performance tests, see Benchmarking. For OS-level tuning, see Performance Tuning. Toolset MinIO provides three dedicated performance testing tools:

AIStor Server implements Erasure Coding as a core component in providing data redundancy and availability. The diagrams and content in this section present a simplified view of erasure coding operations and are not intended to represent the complexities of the AIStor Server’s full erasure coding implementation. MinIO AIStor groups drives in each server pool into one or more Erasure Sets of the same size. By default, each erasure set can contain 2 to 16 drives. You can configure erasure sets up to 32 drives with the MINIO_ERASURE_SET_DRIVE_COUNT environment variable if running AIStor Server RELEASE.2026-02-02T23-40-11Z or later.

MinIO AIStor subscription customers can receive hotfix releases that backport critical fixes to a specific release version without requiring a full upgrade. Hotfixes allow production environments to remain on a standardized release while receiving targeted patches for bugs, regressions, and security vulnerabilities. What is a hotfix A hotfix is a custom build of MinIO AIStor based on a specific release tag with one or more targeted patches cherry-picked from the upstream codebase. Hotfix releases use the naming convention RELEASE.<date>.hotfix to indicate which base release they are built from.

AIStor Server publishes cluster and node metrics using the Prometheus Data Model. You can use any scraping tool to pull metrics data from AIStor Server for further analysis and alerting. This page covers metrics version 3, which has additional metrics and endpoints. Existing deployments can continue to use version 2 metrics. Version 3 endpoints The base endpoint, without an added path, returns cluster, node, and per-bucket statistic metrics from /cluster/usage/buckets.

The MinIO AIStor Operator supports cert-manager to provision and manage certificates, as an alternative to the Operator. cert-manager obtains valid certificates from an Issuer or ClusterIssuer and can automatically renew certificates prior to expiration. A ClusterIssuer issues certificates for multiple Namespaces. An Issuer only mints certificates for its own Namespace. The following instructions implement a self-signed Cluster Issuer. You can also work with other issuers supported by cert-manager. With other issuers, you must provide the Issuer CA certificate to MinIO AIStor, instead of the CAs mentioned in this guide. This example will use cert-manager to issue cluster certificates. The same procedure can be used to issue certificates that can be used outside the cluster. It’s also allowed to let AIStor Operator generate the cluster certificates and use cert-manager to issue the other certificates. Make sure to keep .spec.certificates.disableAutoCert: false to ensure that AIStor Operator will generate the cluster certificates. Summary You complete the following steps to manage your TLS certificates with cert-manager:

This guide covers procedures for rotating TLS certificates in MinIO AIStor deployments without downtime. For certificate setup, see the platform-specific guides under Installation. For troubleshooting certificate errors, see TLS certificate troubleshooting. How MinIO AIStor reloads certificates MinIO AIStor automatically detects certificate changes and reloads them without a restart. Understanding the reload mechanism helps avoid common rotation mistakes.

MinIO AIStor supports publishing audit logs to one or more configured remote webhook receivers. MinIO AIStor send an event for each API operation to the receiver for processing and storage. The receiver is responsible for correctly processing events, including returning 200OK or similar success messages upon receipt of the event. MinIO AIStor cannot recover events that were successfully sent but not correctly stored on the receiver. You can configure a new HTTP audit webhook endpoint using either environment variables or runtime configuration settings: