This page documents settings for controlling MinIO AIStor Tables behavior. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

This page documents settings for configuring a Redis service as a target for Bucket Notifications. See Publish Events to Redis for a tutorial on using these settings. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

This page covers settings that control data healing behavior for the MinIO AIStor process. Healing automatically detects and repairs corrupted or missing data using erasure coding. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

This page documents settings for configuring Security Token Service (STS) behavior in MinIO AIStor. STS provides temporary security credentials for users authenticated through external identity providers such as OpenID Connect or LDAP. You can establish or modify these settings by defining environment variables on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. These settings are environment variables only and do not have corresponding mc admin config settings.

This section provides documentation for integrating applications with MinIO AIStor. Core integration If your application already works with Amazon S3, it can work with MinIO AIStor with minimal configuration changes. Migrating existing S3 applications from AWS to MinIO AIStor typically requires only updating the endpoint URL and credentials in the client configuration.

This page covers deprecated settings that control core behavior of the AIStor Server process. Settings on this page may be removed at any time. Users should migrate to the recommended replacement at the earliest opportunity. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor Server uses the environment variable value.

This section provides guidance around recommended hardware configurations in production AIStor Server deployments. Hardware recommendations The recommendations below reflect our experience with assisting enterprise customers in deploying on a variety of IT infrastructures while maintaining the desired SLA/SLO. Use the recommended configurations below as a guideline for the physical or virtual hosts supporting the AIStor Server deployment. Use the Erasure Code Calculator to provide baseline guidance for the number of hosts and drives necessary to meet your storage and availability requirements.

Protect PersistentVolumeClaims from accidental deletion by adding finalizers to Object Store PVCs.

MinIO 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 MinIO AIStor Object Lambda handler function with a GET request from an application. The handler retrieves the requested object from MinIO AIStor, transforms it, and returns the modified data back to MinIO AIStor to send to the original application. The original object remains unchanged.

AIStor Server includes three groups of environment variables to manage how the server interacts with MinIO KMS, Key Encryption Service (KES), or static key files. You may only define one of the three sets, where defining more that one group results in errors and failure to start. Each configuration setting controls fundamental MinIO AIStor behavior and functionality. Test configuration changes in a lower environment, such as DEV or QA, before applying to production. Define any one set of these environment variables in the host system prior to starting or restarting the MinIO AIStor process. Refer to your operating system’s documentation for how to define an environment variable.