AIStor supports publishing bucket notification events to a AMQP 0-9-1 service endpoint such as RabbitMQ. Prerequisites AMQP 0-9-1 service endpoint. AIStor relies on the https://github.com/streadway/amqp project for AMQP connectivity. The project is primarily tested against RabbitMQ deployments, though other AMQP 0-9-1-compatible services may also work. This procedure assumes a RabbitMQ deployment using the 0-9-1 protocol as the service endpoint.

AIStor supports publishing audit logs to one or more configured remote webhook receivers. AIStor send an event for each API operation to the receiver for processing and storage. The receiver is responsible for correctly processing events, including returning 200OK or similar success messages upon receipt of the event. AIStor cannot recover events that were successfully sent but not correctly stored on the receiver. You can configure a new HTTP audit webhook endpoint using either environment variables or runtime configuration settings:

The mc cp command copies objects to or from an AIStor deployment, where the source can be either an AIStor deployment or a local filesystem. You can also use mc cp against the local filesystem to produce similar results to the cp command-line tool. mc cp copies only the latest version or the specified version of an object without any version information or modification date.

The mc encrypt clear command removes the current default encryption settings for a bucket. Example The following command removes the default encryption settings for the mydata bucket on the AIStor deployment associated with the myaistor alias: mc encrypt clear myaistor/mydata Syntax Syntax The command has the following syntax:

The mc anonymous list retrieves all anonymous (that is, unauthenticated or public) access policies for a bucket. Buckets with anonymous policies allow clients to access the bucket contents and perform actions consistent with the specified policy without authentication. Syntax Example The following command lists all anonymous access policies for the mydata bucket on the myaistor AIStor deployment:

The mc admin user ls command lists all AIStor users on the target AIStor deployment. The mc admin user list command has equivalent functionality to mc admin user ls. mc admin user ls does not return the access key or secret key associated to a user. Use mc admin user info to retrieve detailed user information, including the user access key. To manage external Identity Provider users, see OIDC or AD/LDAP.

Permission This command requires that the user performing it have the admin:Rebalance policy action for the deployment. Description The mc admin rebalance command allows starts, monitors, or stops a rebalancing operation on an AIStor deployment. Rebalancing redistributes objects across all pools in the deployment.

The mc batch generate command creates a basic YAML-formatted template file for the specified job type. After AIStor creates the file, open it in your preferred text editor tool to further customize. You can define one job task definition per batch file. See job types for the supported jobs you can generate. Syntax Example The following command creates a basic YAML file for a replicate job on the mybucket bucket of the myaistor alias.

The mc admin user disable command disables an AIStor user on the target AIStor deployment. Clients cannot use the user credentials to authenticate to the AIStor deployment. Disabling a user does not remove that user from the deployment. Use mc admin user enable to enable a disabled user on an AIStor deployment. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command disables user myuser on the myaistor AIStor deployment:

The mc batch cancel stops an ongoing batch job. You must specify the job ID. To find the job ID, use mc batch list. Syntax Example The following command outputs the job definition for the job identified as KwSysDpxcBU9FNhGkn2dCf.