This section provides documentation and guidance for installing AIStor. Each subsection represents a supported platform, where guidance reflects the specific installation and configuration methods associated with that platform. If you need to install Key Manager to manage cryptographic keys while objects are at rest, see the AIStor Key Manager docs. If you need to install Volume Manager to manage container storage volumes in a Kubernetes environment, see the AIStor Volume Manager docs.

This page documents the steps necessary to add a new AIStor installation to an existing Site Replication configuration. The procedures assumes a new AIStor installations and an existing set of deployments configured for Site Replication. The existing configuration must have all AIStor peer sites reachable and healthy. If any of the sites are unreachable or permanently lost, you must first remove the unreachable site(s) with mc admin replicate rm before expanding with the new site.

This page documents all requirements of bucket replication configurations, including: Active-Passive Active-Active Data Resynchronization Ensure you meet the following prerequisites before you set up any of these replication configurations. Permissions Required for Setting Up Bucket Replication Bucket replication requires specific permissions on the source and destination deployments to configure and enable replication rules.

AIStor supports compressing objects to reduce disk usage. Objects are compressed on PUT before writing to disk, and uncompressed on GET before they are sent to the client. This makes the compression process transparent to client applications and services. Depending on the type of data, compression may also increase overall throughput. Write throughput for a production deployment is generally 500MB per second or greater per available CPU core in the system. Decompression is approximately 1 GB per second or greater for each CPU core.

AIStor bucket notifications allow administrators to send notifications to supported external services when a events occurs on either an object or bucket. AIStor server supports a range of possible events, listed below, that can trigger a notification. AIStor supports bucket and object-level S3 events similar to the Amazon S3 Event Notifications. Supported notification targets AIStor supports publishing event notifications to the following targets:

You can enable versioning using one of the following: At bucket creation AIStor Console (WebUI) AIStor Client CLI Developers can also enable versioning on buckets through an S3-compatible SDK Enable versioning at bucket creation AIStor Console When creating a bucket in the Console, select either Versioned as the bucket Type.

If you integrate AIStor with Active Directory (AD/LDAP) as your identity provider, you can also manage access with AD/LDAP. AIStor can map a user’s Distinguished Name or group Distinguished Names (DNs) to existing policies. See Active Directory/LDAP Identity Management for configuring the integration. This page explains how to create AIStor access policies that match the AD/LDAP DNs. AIStor supports configuring a single Active Directory or LDAP (AD/LDAP) service for external management of user identities.

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.

Install on Kubernetes Deploy AIStor on Kubernetes

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 three steps: Installing AIStor Setting up network encryption Setting up server-side encryption