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...

This procedure explains how to specify the TLS certificates your MinIO AIStor deployment requires and configure your deployment to work with the certificates. See also Enable Network Encryption for explanations of how MinIO AIStor requires TLS and which cipher suites MinIO AIStor supports. Prerequisites The appropriate X.509 certificates for your environment.

Server-Side Encryption (SSE) protects objects as part of write operations, allowing clients to take advantage of server processing power to secure objects at the storage layer (encryption-at-rest). SSE also provides key functionality for regulatory and compliance requirements around secure locking and erasure. MinIO AIStor includes support for deploying MinIO KMS as a dedicated root Key Management Service (KMS) with direct integration. MinIO KMS provides equivalent functionality to other third-party KMS solutions for managing root/external encryption keys in support of encryption operations.

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

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

This guide covers configuring Microsoft Entra ID (formerly Azure Active Directory) as an OpenID Connect (OIDC) identity provider for MinIO AIStor. For general OIDC configuration, see OpenID Connect Identity Management. Prerequisites An active Azure subscription with access to the Azure Portal. A MinIO AIStor deployment with network connectivity to Microsoft identity endpoints. The mc CLI installed and configured with an alias for your MinIO AIStor deployment. Microsoft Graph API permissions MinIO AIStor uses the Microsoft Graph API to query group memberships for authenticated users. The following Application permissions are required (not Delegated):

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

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

MinIO AIStor server-side bucket replication is an automatic bucket-level configuration that synchronizes objects between a source and destination bucket. MinIO AIStor server-side replication requires the source and destination bucket be two separate MinIO AIStor clusters running the same Object Store version. For each write operation to the bucket, MinIO AIStor checks all configured replication rules for the bucket and applies the matching rule with highest configured priority. MinIO AIStor synchronizes new objects and object mutations, such as new object versions or changes to object metadata. This includes metadata operations such as enabling or modifying object locking or retention settings.