AIStor bucket notifications allow administrators to send notifications to supported external services when events occur on objects or buckets, similar to Amazon S3 Event Notifications. This page lists supported event types that trigger notifications, including bucket-level and object-level S3 events. Supported notification targets AIStor supports publishing event notifications to the following targets:

The mc admin accesskey edit command modifies the configuration of an access key associated to the specified user. The command requires that at least one attribute of the access key change. Otherwise, the command exits with an error message. Syntax Example The following command applies a new policy and secret key to the myuserserviceaccount access key on the myaistor deployment:

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.

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.

Description The mc admin policy commands manage policies for use with MinIO Policy-Based Access Control (PBAC). MinIO PBAC uses IAM-compatible policy JSON documents to define rules for accessing resources on an AIStor server. For complete documentation on MinIO PBAC, including policy document JSON structure and syntax, see Access Management. To manage policies for deployments that use LDAP authentication, see mc idp ldap policy.

Description The mc admin group command manages groups on an AIStor deployment. A group is a collection of users. Each group can have one or more assigned policies that explicitly list the actions and resources to which group members are allowed or denied access. Groups provide a simplified method for managing shared permissions among users with common access patterns and workloads.

The mc admin scanner trace command displays scanner-specific API operations occurring on the target AIStor deployment. Syntax Example The following example returns a list of API operations related to the scanner on the myaistor deployment.

The mc admin user enable command enables an AIStor user on the target AIStor deployment. Clients can only use enabled users to authenticate to the AIStor deployment. Users created using mc admin user add are enabled by default. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command enables user myuser on the myaistor AIStor deployment:

The following procedures decommissions one or more pools on a Linux bare-metal deployment. Review the AIStor deployment topology The mc admin decommission command returns a list of all pools in the AIStor deployment: mc admin decommission status myaistor The command returns output similar to the following: ┌─────┬──────────────────────────────────────────────────────────────────┬──────────────────────────────────┬────────┐ │ ID │ Pools │ Capacity │ Status │ │ 1st │ https://aistor-{01...04}.example.com:9000/mnt/disk{1...4}/aistor │ 10 TiB (used) / 10 TiB (total) │ Active │ │ 2nd │ https://aistor-{05...08}.example.com:9000/mnt/disk{1...4}/aistor │ 60 TiB (used) / 100 TiB (total) │ Active │ │ 3rd │ https://aistor-{09...12}.example.com:9000/mnt/disk{1...4}/aistor │ 40 TiB (used) / 100 TiB (total) │ Active │ └─────┴──────────────────────────────────────────────────────────────────┴──────────────────────────────────┴────────┘ The example deployment above has three pools. Each pool has four servers with four drives each.

Run a command from a local or remote npm package