CONTENTS | PREV | NEXT Java Native Interface Specification Contents 1. Introduction Java Native Interface Overview Hi...

Overview MinIO AIStor supports keeping multiple “versions” of an object in a single bucket. When enabled, versioning allows MinIO AIStor to keep multiple iterations of the same object. Write operations which would normally overwrite an existing object instead result in the creation of a new version of the object. MinIO AIStor versioning protects from unintended overwrites and deletions while providing support for “undoing” a write operation. Bucket versioning is a prerequisite for configuring object locking and retention rules.

MinIO AIStor supports deploying resources onto macOS hosts for local development and evaluation. For the purposes of evaluation or local development, MinIO recommends using a machine released in the last 4 years with at least 8 GB of RAM. You can use any supported version of macOS. For testing or local development using a virtualized environment, use a machine with a higher number of cores and 16 or 32GB of RAM.

Mocking OAuth services in testing with Dex

Learn how to create E2B sandboxes with MCP servers, analyze code quality with SonarQube, and generate quality-gated pull requests using GitHub—all through natural language interactions with Claude.

CONTENTS | PREV | NEXT Table of Contents 1 System Architecture 1.1 Overview 1.2 Writing to an Object Stream 1.3 Readi...

Install on Red Hat Enterprise Linux Deploy MinIO AIStor onto RHEL 10+

Configure load balancers and Ingress controllers for MinIO AIStor on Kubernetes. Includes examples for NGINX, HAProxy, and Traefik.

This document describes the process to install Oracle JDK 11 on Windows, Oracle Solaris, macOS, and Linux platforms.

This page describes how to enable FIPS 140-3 ready cryptography for MinIO AIStor deployments on Kubernetes. 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.