MinIO AIStor Documentation MinIO AIStor is a high-performance S3-compatible object store licensed under the MinIO Com...

AIStor supports deploying resources onto Kubernetes infrastructure through our first-party operator model. AIStor also provides a Red Hat OpenShift certified operator. Setting up AIStor on Kubernetes involves three steps: Installing AIStor Setting up network encryption Setting up server-side encryption Kubernetes API Support Production Kubernetes infrastructure should run currently supported releases of the Kubernetes API.

This page explains how to deploy AIStor with KES for Server Side Encryption. For instructions on running KES, see the KES docs. Enabling SSE on an AIStor deployment automatically encrypts the backend data for that deployment using the default encryption key. AIStor requires access to KES and the external KMS to decrypt the backend and start normally. The KMS must maintain access to the MINIO_KMS_KES_KEY_NAME. You cannot disable or reset encryption of the backend.

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. AIStor supports the following types of certificate signatures: self-signed internal or private certificate authorities (CAs)

AIStor supports publishing bucket notification events to PostgreSQL. AIStor supports PostgreSQL 9.5 and later only. Prerequisites PostgreSQL 9.5 and later AIStor relies on features introduced with PostgreSQL 9.5. The AIStor mc Command Line Tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions.