The mc tag command adds, removes, and lists tags associated to a bucket or object. AIStor supports adding up to 10 custom tags to an object. Subcommands mc tag includes the following subcommands: Subcommand Description list List all tags from a bucket or object. remove Remove all tags from a bucket or object. set Set one or more tags on a bucket or object.

The mc support top locks command lists the ten oldest locks on an AIStor deployment. The command outputs the age of the lock, type of lock, owner, and resource. The output resembles the following: Since Type Owner Resource 13 hours ago WRITE 10.68.100.18:9000 .minio.sys/leader.lock 13 hours ago WRITE 10.68.100.18:9000 .minio.sys/callhome/runCallhome.lock 13 hours ago WRITE 10.68.100.23:9000 .minio.sys/new-drive-healing/0/0 Syntax Example The following command displays the current in-progress S3 API calls on the alias myaistor.

The mc version enable command enables versioning on the specified bucket. Syntax Example The following command enables versioning for the mybucket bucket on the myaistor AIStor Object Store:

These sections contain reference material for deploying AIStor Server (minio) resources onto Baremetal infrastructure. AIStor Server uses a binary minio that is a drop-in replacement for the AGPLv3-licensed Community AIStor Server. The minio server command starts the Server process: minio server --license /path/to/minio.license /mnt/disk{1...4} See Installation and Management for a complete guide on installation. Syntax The AIStor Server minio process has a single command minio server.

The mc tag set command sets one or more tags to a bucket or object. AIStor supports adding up to 10 custom tags to an object. Example The following command sets tags for the mydata bucket on the myaistor AIStor deployment: mc tag set myaistor/mydata "tag1=value1&tag2=value2" Syntax The command has the following syntax:

This page documents S3 APIs supported by AIStor Object Store. For reference documentation on any given API, see the corresponding documentation for Amazon S3. Object APIs CopyObject DeleteObject DeleteObjects DeleteObjectTagging GetObject GetObjectAttributes GetObjectTagging

You can use the File Transfer Protocol (FTP) to interact with the objects on an AIStor Server. You must specifically enable FTP or SFTP when starting the server. Enabling either server type does not affect other AIStor Server features. This page uses the abbreviation FTP throughout, but you can use any of the supported FTP protocols described below. Supported protocols When enabled, AIStor supports FTP access over the following protocols:

This page documents environment variables that manage OpenTelemetry-formatted trace information. Trace capture can support ongoing troubleshooting and diagnostics with MinIO Engineering. The information can be relayed to a specified collector, recorded to a local encrypted or unencrypted file, or replayed from a local file to a collector. You can also run the mc support telemetry commands for some of these settings. MINIO_TELEMETRY_TARGET_ENABLE Enable (or disable) telemetry collection on a specified target.

This tutorial explains how to setup a KES Server to use Azure Key Vault as the persistent key store: K E S C l i e n t K E S S e r v e r A z u r e K e y V a u l t Azure Key Vault Azure Key Vault is a managed KMS service that provides a secret store that can be used by KES.

The mc ilm rule import command imports an object lifecycle management configuration and applies it to an AIStor bucket. The mc ilm rule import command imports from STDIN by default. You can input the contents from a .json file, such as one produced by mc ilm rule export. The following command imports the lifecycle management configuration from mydata-lifecycle-config.json and applies it to the mydata bucket on the myaistor deployment: