The mc idp ldap commands allow you to manage configurations to 3rd party Active Directory or LDAP Identity and Access Management (IAM) integrations. AIStor supports multiple named LDAP configurations, allowing you to integrate with different directory services or organizational units within your environment. Multiple LDAP Configurations Support for multiple LDAP configurations requires AIStor Server version RELEASE.2025-12-20T04-58-37Z or later and AIStor Client (mc) version RELEASE.2025-12-19T20-11-44Z or later. The mc idp ldap commands are an alternative to using environment variables when setting up an AD/LDAP connection. They are only supported for AIStor clusters. See Active Directory / LDAP Access Management for a tutorial on using these commands.

mc inventory get retrieves an existing inventory configuration from a bucket. The command displays the configuration details including the bucket name, configuration ID, owner, and the complete YAML definition. Syntax Example The following command retrieves an inventory configuration:

Overview AIStor supports keeping multiple “versions” of an object in a single bucket. When enabled, versioning allows AIStor to keep multiple iterations of the same object. Write operations which would normally overwrite an existing object instead result in the creation of a new version of the object. AIStor versioning protects from unintended overwrites and deletions while providing support for “undoing” a write operation. Bucket versioning is a prerequisite for configuring object locking and retention rules.

AIStor provides multiple replication strategies to ensure data availability, support disaster recovery, enable geographic distribution, and facilitate data migration between clusters. Each replication method serves different use cases and operates at different levels, from entire cluster to individual objects. Replication methods AIStor supports four distinct replication and synchronization approaches:

For identities managed by an external OpenID Connect (OIDC) compatible provider, AIStor can use either of two methods to assign policies to the authenticated user. AIStor by default denies access to all actions or resources not explicitly allowed by a user’s assigned or inherited policies. Authorization options with OIDC OIDC integration in AIStor supports either of the following authorization methods:

Install on Red Hat Enterprise Linux Deploy AIStor onto RHEL 10+

You can suspend bucket versioning at any time using the AIStor Console, the AIStor mc CLI, or using an S3-compatible SDK. Behavior While versioning is suspended, AIStor does the following in the bucket: Objects created while versioning is suspended are assigned a null version ID. Any changes to an object while versioning is suspended result in overwriting that null versioned object. AIStor does not remove or otherwise alter existing versioned objects as part of suspending versioning. Clients can continue interacting with any existing object versions in the bucket. Procedure To disable versioning, select whether you want to use the AIStor Console or the AIStor Client (mc).

AIStor supports deploying resources onto macOS hosts for local development and evaluation. For the purposes of evaluation or local development, MinIO recommends using a machine released in the last 4 years with at least 8 GB of RAM. You can use any supported version of macOS. For testing or local development using a virtualized environment, use a machine with a higher number of cores and 16 or 32GB of RAM.

This page summarizes how a DELETE operation affects objects depending on the configuration of the bucket that contains the object. Any combination of the following factors may impact how DELETE operations function: Bucket versioning Object locking rules Object Lifecycle Management rules Object tiering Site or bucket replication Scanner Permissions AIStor uses a policy based access control system for access management. The user or service account must provide the correct policy action and conditions to allow a DELETE for the bucket and object.

This page documents the steps necessary to remove a peer site from existing Site Replication configuration. Remove the peer site using AIStor Console In a browser, access the Console for one of the existing replicated sites.