Configure batch expiration jobs to immediately expire objects by prefix, age, size, tags, or metadata. Faster than lifecycle rules for bulk cleanup.

MinIO AIStor implements Transport Layer Security (TLS) 1.2+ encryption with support for Server Name Indication (SNI) for selecting relevant TLS certificates in response to client requests. You must set up TLS before you can enable data encryption, also called server-side encryption. See Configure TLS Network Encryption for how to do it on .deb or .rpm based Linux distributions. MinIO AIStor supports the following types of certificate signatures: self-signed internal or private certificate authorities (CAs)

MinIO AIStor implements Transport Layer Security (TLS) 1.2+ encryption with support for Server Name Indication (SNI) for selecting relevant TLS certificates in response to client requests. You must set up TLS before you can enable data encryption, also called server-side encryption. MinIO AIStor supports the following types of certificate signatures: self-signed internal or private certificate authorities (CAs) third-party CAs Multiple certificates are implemented with SNI to determine which certificate to return to a client based on the hostname in the request.

This page documents the steps necessary to initialize site replication between two MinIO AIStor deployments. The procedures assume at least two existing MinIO AIStor installations. Only one of the two sites can have any data at the time of setup. All other sites must be empty of buckets and objects. All sites must otherwise having the following matching configurations: AIStor Server version Key Management Server for Server-Side Encryption Identity Manager Ensure each peer site has a Load Balancer, Reverse Proxy, or similar network control plane component to handle routing connections to its AIStor Server nodes. Using a single node hostname for a peer site creates a single point of failure for site replication where replication can fail if that single node goes down.

The MinIO AIStor Identity Management Plugin provides a REST interface for offloading authentication to an external identity manager with a webhook service. Client applications can use the AssumeRoleWithCustomToken STS API extension to generate access tokens for MinIO AIStor. MinIO AIStor verifies this token by making a POST request to the configured plugin endpoint and uses the returned response to determine the authentication status of the client. Configuration settings You can configure the MinIO AIStor Identity Management Plugin with the following environment variables or configuration settings:

MinIO AIStor supports publishing bucket notification events to PostgreSQL. MinIO AIStor supports PostgreSQL 9.5 and later only. Prerequisites PostgreSQL 9.5 and later MinIO AIStor relies on features introduced with PostgreSQL 9.5. 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.

Configure MinIO AIStor to authenticate users with OpenID Connect providers like Okta, Keycloak, Microsoft Entra ID, or Google for SSO integration.

Use MinIO AIStor Object Lifecycle Management to create rules for time or date based automatic transition or expiry of objects. For object transition, MinIO AIStor automatically moves the object to a configured remote storage tier. For object expiry, MinIO AIStor automatically deletes the object. MinIO AIStor derives its behavior and syntax from S3 lifecycle for compatibility in migrating workloads and lifecycle rules from S3 to MinIO AIStor. For example, you can export S3 lifecycle management rules and import them into MinIO AIStor or vice-versa. MinIO AIStor uses JSON to describe lifecycle management rules and may require conversion to or from XML as part of importing S3 lifecycle rules.

Configure MinIO AIStor to authenticate users against Active Directory or LDAP directory services with support for multiple providers.

MinIO AIStor supports publishing bucket notification events to MQTT server/broker endpoint. Prerequisites MQTT 3.1 or 3.1.1 Server/Broker This procedure assumes an existing MQTT 3.1 or 3.1.1 server/broker to which the AIStor Server has connectivity. See the mqtt.org software listing for a list of MQTT-compatible server/brokers.