Description The mc event command supports adding, removing, and listing bucket event notifications. AIStor automatically sends triggered events to the configured notification targets. AIStor supports notification targets like AMQP (RabbitMQ), Redis, ElasticSearch, NATS and PostgreSQL. See Bucket Notifications for more information. Subcommands mc event includes the following subcommands:

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.

Use AIStor Object Lifecycle Management to create rules for time or date based automatic transition or expiry of objects. For object transition, AIStor automatically moves the object to a configured remote storage tier. For object expiry, AIStor automatically deletes the object. AIStor derives its behavior and syntax from S3 lifecycle for compatibility in migrating workloads and lifecycle rules from S3 to AIStor. For example, you can export S3 lifecycle management rules and import them into AIStor or vice-versa. AIStor uses JSON to describe lifecycle management rules and may require conversion to or from XML as part of importing S3 lifecycle rules.

Server-Side Encryption (SSE) protects objects as part of write operations, allowing clients to take advantage of server processing power to secure objects at the storage layer (encryption-at-rest). SSE also provides key functionality for regulatory and compliance requirements around secure locking and erasure. AIStor includes support for deploying AIStor Key Manager as a dedicated root Key Management Service (KMS) with direct integration. Key Manager provides equivalent functionality to other third-party KMS solutions for managing root/external encryption keys in support of encryption operations.

AIStor requires authentication and authorization for every operation on the object store. Human users and client applications must authenticate, and can perform only operations on resources explicitly allowed by the access policies assigned to them. Authentication verifies the identity of a user or client application. User credentials take the form of a username and password. Application credentials can take the form of an access key and secret key, or an application can call the appropriate STS endpoint. Which endpoint depends on your identity provider.

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

The AIStor Access Management Plugin provides a REST interface for offloading authorization through a webhook service. AIStor sends the request and credential details for every API call to the configured external HTTP(S) endpoint and looks for a response of ALLOW or DENY. AIStor can therefore delegate the access management to the external system instead of relying on S3 policy based access control. Configuration Settings You can configure the AIStor External Access Management Plugin using the following environment variables or configuration settings.

This section documents steps for installing and managing AIStor Server on macOS™ host machines. Procedure Install AIStor Server onto the macOS host The easiest way to install AIStor Server on macOS is using Homebrew. Alternatively, AIStor provides binaries for M-series processors (ARM64) and older Intel-based processors (AMD64). Download the binary, set it as executable, and copy it to a location in your $PATH such as /usr/local/bin

The AIStor Client command line tool includes the mc admin subcommand tree for performing administrative tasks on your AIStor deployments. mc admin target AIStor deployments exclusively and do not support any other S3-compatible service. The command has the following top-level syntax. Use the --help parameter to view the CLI help. mc admin [FLAGS] COMMAND [ARGUMENTS] Global Options mc admin supports the same global options as mc. See Global Options.

The mc admin accesskey disable command disables an existing access key for a MinIO IDP user. Syntax Example The following command disables the specified access key: