This page describes how to upgrade AIStor Helm deployments that use public registries and have direct internet access to helm.min.io and quay.io. If your deployment uses a private container registry or is in an airgapped environment, see: Upgrade with Private Registry Upgrade in Airgapped Environment Overview AIStor Helm upgrades involve updating two components:

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.

AIStor supports publishing bucket notification events to a webhook service endpoint. Prerequisites The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add a webhook endpoint to an AIStor Server The following procedure adds a new webhook service endpoint for supporting bucket notifications in an AIStor Server.

AIStor supports decommissioning and removing server pools from a deployment with two or more pools. To decommission, there must be at least one remaining pool with sufficient available space to receive the objects from the decommissioned pools. AIStor supports queueing multiple pools in a single decommission command. Each listed pool immediately enters a read-only status, but draining occurs one pool at a time. Decommissioning is designed for removing an older server pool whose hardware is no longer sufficient or performant compared to the pools in the deployment. AIStor automatically migrates data from the decommissioned pools to the remaining pools in the deployment based on the ratio of free space available in each pool.

The AIStor Client (mc) is a drop-in replacement for the Open Source MinIO client. AIStor mc has exclusive functionality intended to support licensed AIStor Server deployments. mc has the following syntax: mc [GLOBALFLAGS] COMMAND --help See Command quick reference for a list of supported commands. Command name Some operating systems bundle another software tool that uses mc as its command name. In those cases, the AIStor Client uses the command mcli instead. Swap mcli in for mc in all reference documentation if this is your situation.

Healing is AIStor’s ability to restore an object that has been damaged, corrupted, or partially lost. The loss can come from multiple types of corruptions or loss, such as but not limited to: drive-level errors or failure OS or filesystem errors or failure bit rot Healing and erasure coding AIStor can restore a damaged object depending on the following variables;

You can apply bucket rate limiting and concurrency rules to any of the following APIs: S3 Bucket metadata operations s3.GetBucketLocation s3.GetBucketPolicy s3.GetBucketEncryption s3.GetBucketLifecycleConfiguration s3.GetBucketVersioning s3.GetBucketTagging s3.GetBucketACL s3.GetBucketCORS s3.GetBucketWebsite s3.GetBucketNotificationConfiguration s3.GetObjectLockConfiguration s3.GetBucketReplicationConfiguration Bucket configuration operations s3.PutBucket s3.PutBucketPolicy s3.PutBucketEncryption s3.PutBucketLifecycleConfiguration s3.PutBucketVersioning s3.PutBucketTagging s3.PutBucketACL s3.PutBucketNotificationConfiguration s3.PutObjectLockConfiguration s3.PutBucketReplicationConfiguration Bucket deletion operations s3.DeleteBucket s3.DeleteBucketPolicy s3.DeleteBucketTagging s3.DeleteBucketWebsite s3.DeleteBucketLifecycleConfiguration s3.DeleteBucketEncryption s3.DeleteBucketReplicationConfiguration Object read operations s3.GetObject s3.GetObjectAttributes s3.GetObjectACL s3.GetObjectTagging s3.GetObjectRetention s3.GetObjectLegalHold s3.HeadObject Object write operations s3.PutObject s3.PutObjectExtract s3.PutObjectACL s3.PutObjectTagging s3.PutObjectRetention s3.PutObjectLegalHold s3.CopyObject Object deletion operations s3.DeleteObject s3.DeleteObjects s3.DeleteObjectTagging Object listing operations s3.ListObjectsV2 s3.ListObjectVersions s3.ListobjectsV1 s3.ListBuckets Multipart upload operations s3.NewMultipartUpload s3.UploadPart s3.UploadPartCopy s3.CompleteMultipartUpload s3.AbortMultipartUpload s3.ListMultipartUploads s3.ListObjectParts Other operations s3.SelectObjectContent s3.RestoreObject s3.PostPolicy s3.ListenNotification s3.ReplicationResyncStatus s3.ReplicationResyncStart SFTP operations sftp.GET sftp.PUT sftp.LIST sftp.STAT sftp.MKDIR sftp.RMDIR sftp.REMOVE

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:

The mc admin accesskey enable command enables an existing access key. The command requires the access key to exist and be currently disabled. Syntax Example The following command enables the access key myuseraccesskey on the myaistor deployment:

The mc admin accesskey rm command removes an access key associated to a user on the deployment. The command requires the access key to exist. Syntax Example The following command removes the access key myuseraccesskey from the myaistor deployment: