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.

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

Each procedure on this page creates a new object lifecycle management rule that expires objects on an MinIO AIStor bucket. This procedure supports use cases like removing “old” objects after a certain time period or calendar date. Requirements Install and configure AIStor Client This procedure uses the AIStor Client (mc) for performing operations on the MinIO AIStor cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.

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

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.

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

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:

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