AIStor’s Object Lambda enables developers to programmatically transform objects on demand. You can transform objects as needed for your use case, such as redacting personally identifiable information (PII), enriching data with information from other sources, or converting between formats. Overview An Object Lambda handler is a small code module that transforms the contents of an object and returns the results. Like Amazon S3 Object Lambda functions, you trigger an AIStor Object Lambda handler function with a GET request from an application. The handler retrieves the requested object from AIStor, transforms it, and returns the modified data back to AIStor to send to the original application. The original object remains unchanged.

Go GitHub: minio/minio-go You can install the Go SDK using the following command: go get github.com/minio/minio-go/v7 Quickstart: Go Quickstart Reference: Go API docs Python GitHub: minio/minio-py

The AIStor Security Token Service (STS) AssumeRoleWithCustomToken API endpoint generates a token for use with the AIStor External Identity Management Plugin. Request endpoint The AssumeRoleWithCustomToken endpoint has the following form: POST https://aistor.example.net?Action=AssumeRoleWithCustomToken[&ARGS] The following example uses all supported arguments. Replace the aistor.example.net hostname with the appropriate URL for your AIStor cluster:

Drive type MinIO recommends using flash-based storage (NVMe or SSD) for all workload types at any scale. Workloads that require high performance should prefer NVMe over SSD. For best performance, use 30+TB drives with NVMe over PCIe 4.0 or 5.0. Directly attached storage For best performance, provide AIStor with drives attached directly to each host node as a JBOD array with no RAID or similar management layers. AIStor requires the XFS filesystem for best performance and behavior at scale. Using any other type of backing storage (SAN/NAS, ext4, RAID, LVM) typically results in a reduction in performance, reliability, predictability, and consistency.

The MinIO JavaScript Client SDK provides high level APIs to access any Amazon S3 compatible object storage server. This guide will show you how to install the client SDK and execute an example JavaScript program. For a complete list of APIs and examples, please take a look at the JavaScript Client API Reference documentation. This document presumes you have a working Node.js development environment, LTS versions v16, v18 or v20.

This tutorial deploys AIStor onto Kubernetes distributions that follow the upstream API and functionality. The steps in this procedure may work on forked Kubernetes distributions. This procedure requires the installation of Kubernetes operators and associated resources including CustomResourceDefinitions, StatefulSets, and secrets into new or existing namespaces. You must perform the operations in this procedure as a user that has broad permissions to create resources within multiple namespaces. Deploy AIStor using Helm This procedure documents installation on Kubernetes with the AIStor Helm Charts. MinIO recommends Helm version 3.17 or later.

MinIO announced AIStor Tables as a Technical Preview on September 30th, 2025. AIStor Tables implements native Iceberg tables support in AIStor object storage. This feature allows users to create, manage, and query Iceberg tables directly through AIStor Object Store with no dependencies on external catalog services or metadata databases. AIStor Tables implements a subset of the Iceberg REST Catalog spec functions. Applications can interact with Iceberg entities through the AIStor Iceberg API while performing S3 operations through the object storage API.

The mc version info command returns the versioning status for the specified bucket. Syntax Example The following command returns the versioning status for the mybucket bucket on the myaistor AIStor deployment:

The mc stat command displays information on objects in an AIStor bucket, including object metadata. You can also use it to retrieve bucket metadata. You can use mc stat against the local filesystem to produce similar results to the stat command-line tool. Syntax Example The following command displays information on all objects in the mydata bucket on the myaistor AIStor deployment:

The mc support perf net command measures the network throughput of all nodes in a cluster. Use this command to identify potential network performance bottlenecks in your deployment. Syntax Example The following command runs a network throughput test on a cluster with alias myaistor.