This page documents environment variables that manage OpenTelemetry-formatted trace information for the AIStor Server. Trace capture can support ongoing troubleshooting and diagnostics with MinIO Engineering. The information can be relayed to a specified collector, recorded to a local encrypted or unencrypted file, or replayed from a local file to a collector. You can also run the mc support telemetry commands for some of these settings.

Configure AIStor Operator behavior with environment variables. Includes TLS settings, namespace watching, Prometheus integration, and OpenTelemetry support.

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, AIStor uses the environment variable value.

This page documents S3 APIs supported by AIStor Object Store. For reference documentation on any given API, see the corresponding documentation for Amazon S3. Object APIs CopyObject DeleteObject DeleteObjects DeleteObjectTagging GetObject GetObjectAttributes GetObjectTagging

AIStor supports deploying resources as a container for local development and evaluation. Setting up AIStor as a container involves these steps: Deploy AIStor as a container Set up network encryption (optional) Performance The following table shows areas that have the greatest impact on AIStor performance, listed in order of importance.

AIStor supports deploying resources onto Linux infrastructures and provides packages for Red Hat Enterprise Linux and Ubuntu Server platforms. Setting up AIStor on Linux involves these steps: Install AIStor Configure load balancing Set up network encryption Set up server-side encryption Enable FIPS mode (optional, for regulatory compliance)

You can exclude up to 10 prefixes on a bucket with versioning enabled. This is especially useful for Spark or Hadoop workloads or any process that initially creates objects with temporary prefixes. Prefixes A prefix is a common leading string of characters under a bucket that a set of objects share.

Each procedure on this page creates a new object lifecycle management rule that expires objects on an AIStor bucket. This procedure supports use cases like removing “old” objects after a certain time period or calendar date. Requirements Install and configure AIStor Client This procedure uses the AIStor Client (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.

In rare circumstances, you may need to restore site replication service account information to a peer in the cluster. Seeing AccessDenied for site replication calls either in logs or with :mc-cmd:mc admin trace indicates a need to restore service account information to a peer. This error typically results when the service accounts for site replication of one of the peer sites have been lost or corrupted. Procedure To restore the required information, export the service account information from an existing healthy peer site and import it to the site with the missing account information.

Configure AIStor to authenticate users with OpenID Connect providers like Okta, Keycloak, Microsoft Entra ID, or Google for SSO integration.