expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Hide navigatio...

expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

Site replication configures multiple independent AIStor deployments as a cluster of replicas called peer sites. Site replication assumes the use of either the included AIStor identity provider (IDP) or an external IDP. All configured deployments must use the same IDP. Deployments using an external IDP must use the same configuration across sites. AIStor does not recommend using MacOS, Windows, or non-orchestrated Containerized deployments for site replication outside of early development, evaluation, or general experimentation.

AIStor uses Policy-Based Access Control (PBAC) to define the authorized actions and resources to which an authenticated user has access. Each policy describes one or more actions and conditions that outline the permissions of a user or group of users. AIStor PBAC is built for compatibility with AWS IAM policy syntax, structure, and behavior. This documentation makes a best-effort to cover IAM-specific behavior and functionality. Refer also to the AWS IAM documentation for more information.

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 storage 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.

Syntax The mc ilm rule export command exports the object lifecycle management configuration for an AIStor bucket. The mc ilm rule export command outputs to STDOUT by default. You can output the contents to a .json file for archival or ingestion using mc ilm rule import.

The mc idp ldap add command creates an AD/LDAP IDP server configuration. AIStor supports no more than one (1) AD/LDAP provider per deployment. Syntax Example The following example sets the AD/LDAP configuration settings for the myminio deployment.

The mc event ls command lists all event notification triggers for a bucket. The alias mc event list has equivalent functionality to mc event ls. Syntax EXAMPLE The following command lists all configured event notifications for the specified bucket notification target for the mydata bucket on the myminio AIStor deployment:

The mc admin cluster iam import command imports IAM metadata as created by the mc admin cluster iam export command. You can use this command to manually restore IAM metadata settings for an AIStor deployment. The command outputs the results of the import, including the following: count of individual entities imported by entity type list of policies imported by entity type they imported to list of entities that failed to import Syntax Example The following command imports the IAM metadata of the specified file onto the myminio deployment.