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

This page describes how to enable FIPS 140-3 ready cryptography for MinIO AIStor deployments on Linux. When enabled, FIPS mode restricts cryptographic operations to algorithms that align with the Federal Information Processing Standards (FIPS) 140-3 program. Organizations subject to U.S. federal government compliance requirements, or those with similar regulatory needs, may require FIPS-aligned cryptography. MinIO AIStor FIPS mode uses Go’s native cryptographic module, which restricts operations to FIPS 140-3 approved algorithms. MinIO makes no statements or representations regarding FIPS 140-3 certification status. Evaluate whether this implementation meets your specific compliance requirements. Overview MinIO AIStor uses Go 1.24’s native FIPS 140-3 cryptographic module. Enable FIPS mode at runtime with the GODEBUG environment variable. There is no separate binary required.

Use the following checklist when planning the software configuration for a production, distributed MinIO deployment. MinIO AIStor pre-requisites Operating system Servers must run a Linux operating system with a kernel version of 6.8 or later to access critical performance features.

You may create objects whose sole purpose is organizing a bucket. These objects end with the / character. Versioning is often not of value for these types of objects that have no data. For example, an object at ALIAS/team-bucket/reports may serve as an organization path only and not be a data object. Instead, it contains objects under it, such as ALIAS/team-bucket/reports/2025/june.csv. You may exclude folder objects to prevent ALIAS/team-bucket/reports from being versioned while allowing all objects under it to be versioned.

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

For identities managed by an external OpenID Connect (OIDC) compatible provider, MinIO AIStor can use either of two methods to assign policies to the authenticated user. MinIO AIStor by default denies access to all actions or resources not explicitly allowed by a user’s assigned or inherited policies. Authorization options with OIDC OIDC integration in MinIO AIStor supports either of the following authorization methods:

MinIO AIStor is licensed under the MinIO Software License. An active license is required for production deployments. This section documents steps for running MinIO AIStor as a container. Procedure Pull the latest stable image of AIStor Server Docker docker pull quay.io/minio/aistor/minio Podman podman pull quay.io/minio/aistor/minio Create the directory structure Create directories for data and certificates. The following example uses $HOME/minio as the base path.

The procedure on this page creates a new object lifecycle management rule that transition objects from an MinIO AIStor bucket to a remote storage tier on the storage backend. This procedure supports use cases like moving aged data to low-cost public cloud storage solutions after a certain time period or calendar date. Requirements Install and configure mc This procedure uses 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...

Use the following checklist when planning the security configuration for a production, distributed AIStor Server. Required steps Identity and access management Step Details Group policies Define group policies either on MinIO AIStor or the selected 3rd party Identity Provider (LDAP/Active Directory or OpenID Connect) Individual access policies Define individual access policies on MinIO AIStor or the selected 3rd party Identity Provider Identity provider configuration Configure MinIO AIStor to use the selected 3rd party Identity Provider Firewall access Port Details S3 API listen port Grant firewall access for TCP traffic to the Object Store S3 API Listen Port (Default: 9000) Console port Grant firewall access for TCP traffic to the AIStor Server console port (Recommended Default: 9443) Encryption-at-rest MinIO AIStor supports Server-Side Encryption using MinIO KMS: