This section documents steps for running 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.

This page explains how to deploy AIStor with KES for Server Side Encryption. For instructions on running KES, see the KES docs. Broadly, the required steps are: Create a new external key (EK) for server-side encryption (SSE). Create or modify an AIStor deployment to support SSE with KES. Configure automatic bucket-default SSE. Enabling SSE on an AIStor deployment automatically encrypts the backend data for that deployment using the default encryption key.

The procedure on this page creates a new object lifecycle management rule that transition objects from an 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 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.

Deployment Checklists The following checklists provide a high-level guideline for validating production-readiness of AIStor Servers. These checklists may not meet the precise requirements of your unique deployment topology or architecture, and are intended as a best-effort guide to reliable production deployments.

The mc put command uploads objects from a local filesystem to an AIStor deployment. You can also use mc put to upload objects to S3-compatible services. Syntax Example The following command uploads a file from the local filesystem to the myaistor deployment:

The mc support telemetry record command streams captured trace calls to a file. Use the --sample flag to modify the number of calls traced and adjust the impact on performance. In addition to creating a file with the telemetry data, the command outputs the number of packets saved, the file name and path, and instructions for uploading the generated file to SUBNET. You can replay a recorded file and stream the telemetry to an OpenTelemetry Protocol (OTLP)-compatible collector by HTTP interface with mc support telemetry replay. You can also analyze the recorded file locally with an interactive terminal interface using mc support telemetry analyze.

The mc support diag command generates a health report for an AIStor deployment. The command generates and uploads the health report to SUBNET for analysis. Automated with Call Home The report is automatically generated and uploaded every 24 hours with Call Home, which can be disabled or enabled at any time. The resulting health report is intended for use by MinIO Engineering through SUBNET and may contain internal or private data points. Exercise caution before sending a health report to a third party or posting the health report in a public forum.

Use the mc support perf command to review the performance of the S3 API (read/write), network IO, and storage (drive read/write). The resulting tests can provide general guidance of deployment performance under S3 GET and PUT requests and identify any potential bottlenecks. For more complete performance testing, consider using a combination of load-testing using your staging application environments and the MinIO Warp S3 benchmarking tool. The command has the following syntax:

The mc idp ldap disable command disables an AD/LDAP provider configuration. Syntax Example The following example disables the default AD/LDAP configuration on the myaistor deployment.

The mc rm command removes objects from a bucket on an AIStor deployment. To completely remove a bucket, use mc rb instead. You can also use mc rm against the local filesystem to produce similar results to the rm command-line tool. For more information on how AIStor performs DELETE actions on objects, see Object Deletion. mc rm supports removing multiple objects or files in a single command. Consider using the --dry-run option to validate that the operation targets only the desired objects/files.