The mc support diag command generates a health report for an AIStor deployment. The command generates and uploads the health report to SUBNET for analysis. Automated with Call Home The report is automatically generated and uploaded every 24 hours with Call Home, which can be disabled or enabled at any time. The resulting health report is intended for use by MinIO Engineering through SUBNET and may contain internal or private data points. Exercise caution before sending a health report to a third party or posting the health report in a public forum.

The mc support telemetry replay command replays a file of telemetry data to an OpenTelemetry collector. You can record a file to replay later with mc support telemetry record. Syntax Example The following command replays a local file of telemetry data to a localhost OTLP server.

This page documents environment variables for configuring AIStor to use drive-level cache for frequently accessed objects. When enabled, AIStor caches the metadata of accessed objects to node memory on PUT and GET requests. When the available memory reaches capacity, AIStor ejects the oldest last-accessed object from the cache. This keeps the most frequently accessed objects in the cache. Cache configuration settings control fundamental AIStor behavior and functionality. Test configuration changes in a lower environment, such as DEV or QA, before applying to production. Enable Environment Variable MINIO_CACHE_ENABLE Configuration Setting There is no configuration setting for this variable, as these settings apply at server startup. Set to on to use the drive cache feature.

Entrust KeyControl is a proprietary KMS which KES supports using for storing secrets. K E S C l i e n t K E S S e r v e r E n t r u s t K e y C o n t r o l Prerequisites This procedure was written and tested against Entrust KeyControl v10.1. The provided instructions may work against other KeyControl versions. This procedure assumes you have prior experience with Entrust products and have followed their documentation, best practices, and other published materials in deploying the KeyControl service.

Operations

AIStor Key Manager supports installation on Linux hosts running AMD64 or ARM64 architectures. This procedure downloads and installs the Key Manager onto a single host machine. You can then expand the cluster with additional nodes to increase availability and resiliency. For production environments, ensure a minimum of 3 key manager hosts. Procedure The commands in this procedure may require sudo permissions to succeed depending on the level of access you have when accessing the host machine. If you do not have sudo or similar permissions, contact your systems administrator for assistance with completing the steps in this procedure.

Overview Use the kes identity commands to generate the API key of an PEM key file. In addition, you can use subcommands to temporarily manage the identities that access the KES server. Use the subcommand to display, create, or remove identities. All changes made by kes identity subcommands are lost when the KES server restarts. To make persistent changes to KES identities, modify the Policies and Identities section of the KES configuration file. Specifically, for each policy.policyname to modify, add/remove the identities to/from the policy.policyname.identities array.

Overview Starts a stateful KES server or cluster. Syntax kes init \ --config <PATH> \ --force, -f Parameters --config Path to the configuration file to use for the server or cluster.

This section provides reference documentation for the AIStor Key Encryption Service (KES). This KES is distinct from the AGPL3.0-licensed community KES.

Overview Return the name, ID, and creation information about a cryptographic key. Output resembles the following: Name my-key ID 14eb17aec10cd31a6bc006ba81d63589 Created At 2023-03-09 18:16:11 Created By 3ecfcdf38fcbe141ae26a1030f81e96b753365a46760ae6b578698a97c59fd22 Syntax kes key info \ <name> \ [--color <string>] \ [--insecure, -k] \ [--json] Parameters name Required