You can manage human and application users for your AIStor deployment with either the mc command-line tool or the AIStor console. You create these users and assign policies to them. You can also create groups of users to assign policies to. See Identity and Access Management. This page explains how to work with the built-in AIStor identity management solution. You can integrate with other identity management solutions: OpenID Connect (OIDC)

AIStor supports publishing bucket notification events to a webhook service endpoint. Prerequisites The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add a webhook endpoint to an AIStor Server The following procedure adds a new webhook service endpoint for supporting bucket notifications in an AIStor Server.

The AIStor Identity Management Plugin provides a REST interface for offloading authentication to an external identity manager with a webhook service. Client applications can use the AssumeRoleWithCustomToken STS API extension to generate access tokens for AIStor. AIStor verifies this token by making a POST request to the configured plugin endpoint and uses the returned response to determine the authentication status of the client. Configuration settings You can configure the AIStor Identity Management Plugin with the following environment variables or configuration settings:

The procedure on this page resynchronizes the contents of an AIStor bucket using a healthy replication remote. Resynchronization supports recovery after partial or total loss of data on an AIStor deployment in a replica configuration. For example, consider an AIStor active-active replication configuration similar to the following: Resynchronization allows using the healthy data on one of the participating AIStor deployments as the source for rebuilding the other deployment.

AIStor supports publishing bucket notification events to PostgreSQL. AIStor supports PostgreSQL 9.5 and later only. Prerequisites PostgreSQL 9.5 and later AIStor relies on features introduced with PostgreSQL 9.5. The AIStor mc Command Line Tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions.

This section of the documentation provides information on: Identity and access management (IAM) Policies Users Groups Objects Versioning Locking and immutability Lifecycle management Bucket notifications Replication Site replication Bucket replication Batch replication Server-side encryption

You may create objects whose sole purpose is organizing a bucket. These objects end with the / character. Versioning is often not of value for these types of objects that have no data. For example, an object at ALIAS/team-bucket/reports may serve as an organization path only and not be a data object. Instead, it contains objects under it, such as ALIAS/team-bucket/reports/2025/june.csv. You may exclude folder objects to prevent ALIAS/team-bucket/reports from being versioned while allowing all objects under it to be versioned.

Use the following checklist when planning the security configuration for a production, distributed AIStor Server. Required steps Step ☐ Define group policies either on AIStor or the selected 3rd party Identity Provider (LDAP/Active Directory or OpenID). ☐ Define individual access policies on AIStor or the selected 3rd party Identity Provider. ☐ Configure AIStor to use the selected 3rd party Identity Provider. ☐ Grant firewall access for TCP traffic to the Object Store S3 API Listen Port (Default: 9000). ☐ Grant firewall access for TCP traffic to the AIStor Server console port (Recommended Default: 9443). Encryption-at-Rest AIStor Object Store supports Server-Side Encryption using AIStor Key Manager:

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 Google Cloud Storage (GCS) 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.

Healing is AIStor’s ability to restore an object that has been damaged, corrupted, or partially lost. The loss can come from multiple types of corruptions or loss, such as but not limited to: drive-level errors or failure OS or filesystem errors or failure bit rot Healing and Erasure Coding AIStor can restore a damaged object depending on the following variables;