This page documents environment variables for configuring MinIO AIStor to publish data to an HTTP webhook endpoint and trigger an Object Lambda function. See Transforms with Object Lambda for more complete documentation and tutorials on using these environment variables. Environment Variables You can specify multiple targets by appending a unique identifier _ID for each set of related settings.

This page covers settings that control bucket and site replication behavior for the MinIO AIStor process. 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.

The MinIO AIStor Security Token Service (STS) AssumeRoleWithWebIdentity API endpoint generates temporary access credentials using a JSON Web Token (JWT) returned from a configured OIDC Identity Provider (IDP). This page documents the AIStor Server AssumeRoleWithWebIdentity endpoint. For instructions on implementing STS using an S3-compatible SDK, refer to the documentation for that SDK. The MinIO AIStor STS AssumeRoleWithWebIdentity API endpoint is modeled after the AWS AssumeRoleWithWebIdentity endpoint and shares certain request/response elements. This page documents the AIStor-specific syntax and links out to the AWS reference for all shared elements.

The following section documents environment variables for configuring MinIO AIStor to publish audit logs to an HTTP webhook endpoint. See Publish Audit Logs to HTTP Webhook for more complete documentation and tutorials on using these environment variables. Example Environment Variables You can specify multiple webhook endpoints as audit log targets by appending a unique identifier _ID for each set of related logging settings.

The pages in this section document settings for configuring MinIO AIStor to work with identity and access management (IAM) solutions. There is a page of settings for each of the IAM methods MinIO AIStor supports. Active Directory / LDAP OpenID Connect Security Token Service (STS) MinIO Identity Management Plugin MinIO Access Management Plugin

Reference documentation for the MinIO AIStor Operator on Kubernetes. Includes CRD specifications, Helm chart values, environment variables, and AdminJob configuration.

The following page includes the full contents of the AIStor Server Operator Helm Chart default values.yaml and all accompanying documentation. Configuration precedence The MinIO AIStor Operator Helm chart supports a hierarchical configuration system where settings can be defined at multiple levels. When the same setting is defined at multiple levels, the following order of precedence determines which value is used (highest to lowest):

Configure OpenTelemetry logging for the MinIO AIStor Operator. Export structured logs to OTLP collectors for centralized observability and troubleshooting.

Memory primarily constrains the number of concurrent simultaneous connections per node. MinIO recommends at least 256GiB of RAM per host. MinIO AIStor allocates up to 75% of host memory to support GET operations. Ensure you size your host memory such that the remaining available host memory supports your target number of concurrent connections per host. You can calculate the maximum number of concurrent requests per node with this formula: $$(0.75 * totalRam) / ramPerRequest$$ramPerRequest is typically 2MiB, which is two times the default erasure block size. For questions about adjusting the erasure block size for your use case, create a SUBNET issue to discuss with MinIO engineers.

The following page includes the full contents of the AIStor Server Helm Chart default values.yaml and all accompanying documentation. Removed fields The objectStore.features section (.spec.features in the CRD) has been fully removed in Operator RELEASE.2025-12-16T20-51-03Z. This section includes the following fields that previously provided shortcuts for common configurations.