The procedure on this page creates a new bucket replication rule for one-way synchronization of objects from one AIStor bucket to another AIStor bucket. The buckets can be on the same AIStor deployment or on separate AIStor deployments. Requirements Replication requires all participating clusters meet the bucket replication requirements. This procedure assumes you have reviewed and validated those requirements.

The largest value that can be represented by this integer type. Use `u8::MAX` instead.

AIStor Server supports publishing bucket notification events to an Elasticsearch service endpoint. Prerequisites Elasticsearch v7.0 or later. AIStor relies on the v7 project for Elastic connectivity. The elastic/v7 library specifically targets Elasticsearch v7.0 and is not compatible with earlier Elasticsearch versions. The AIStor mc command line tool.

AIStor provides tools for scaling your cluster capacity by adding or removing server pools. These tools allow you to expand storage capacity or retire aging hardware without disrupting ongoing operations. Planning for growth MinIO recommends initially sizing clusters for at least 2-3 years of anticipated data growth. This approach minimizes the frequency of expansion operations and simplifies long-term capacity management.

You can use the AIStor Console to perform several of the identity and access management functions available in AIStor, such as: Create and manage user credentials or groups with the built-in AIStor IDP, connect to one or more OIDC providers, or add an LDAP provider for Single Sign On. Configure single sign on workflows using either OpenID Connect or AD/LDAP. View, manage, and create access policies. Create child access keys that inherit the parent’s permissions. IAM Users The IAM Users section provides a management interface for AIStor-managed users.

Basic mathematical constants.

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:

The largest value that can be represented by this integer type. Use `u16::MAX` instead.

Each AIStor server process exposes unauthenticated endpoints for probing server uptime and deployment high availability for simple healthchecks. These endpoints return an HTTP status code indicating whether the underlying resource is healthy or satisfies read/write quorum. The server exposes no other data through these endpoints. AIStor liveness Use the following endpoint to test if the specified AIStor server is up and ready to serve requests:

An anchor in time which can be used to create new `SystemTime` instances or learn about where in time a `SystemTime` lies.