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:

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

The mc admin cluster bucket export command exports bucket metadata for use with the (mc admin cluster bucket import) command. You can use this command to manually back up the metadata for the specified MinIO AIStor bucket. The command always saves the output as cluster-metadata.zip. If you specify only the deployment as the target, this command backs up all bucket metadata on the target deployment.

The mc admin accesskey edit command modifies the configuration of an access key associated to the specified user. The command requires that at least one attribute of the access key change. Otherwise, the command exits with an error message. Syntax Example The following command applies a new policy and secret key to the myuserserviceaccount access key on the myaistor deployment:

Troubleshoot common upgrade issues including KES certificates, PolicyBinding errors, OperatorHub subpath problems, and object store failures.

This page describes how to upgrade MinIO AIStor Helm clusters that use a private container registry but have internet access to helm.min.io for chart updates. If your cluster uses public registries or is in an airgapped environment, see: Upgrade with Public Registries Upgrade in Airgapped Environment Overview MinIO AIStor Helm upgrades involve updating two components:

The mc admin accesskey enable command enables an existing access key. The command requires the access key to exist and be currently disabled. Syntax Example The following command enables the access key myuseraccesskey on the myaistor deployment:

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

MinIO AIStor supports expanding an existing distributed cluster by adding a new server pool. Each pool expands the total available storage capacity of the cluster. MinIO AIStor does not support increasing storage through logical volume expansion, rolling drive replacement, or other filesystem-level approaches. Expansion does not provide Business Continuity/Disaster Recovery (BC/DR)-grade protections. While each pool is an independent set of servers with distinct erasure sets for availability, the complete loss of one pool results in MinIO stopping I/O for all pools in the cluster. Similarly, an erasure set which loses quorum in one pool represents data loss of objects stored in that set, regardless of the number of other erasure sets or pools.