This page covers settings that control root (superuser) access for the AIStor process. The root user has complete access and permissions to perform operations on the AIStor deployment. Root User and Root Password are required even if you use the MinIO Key Encryption Service or other key management utility. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

This section documents settings that control behavior related to AIStor metrics and logging. See Metrics and Alerts for more information. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

Use the REST API to create and manage security campaigns for your organization.

Change the owner and group of the file referenced by the specified open file descriptor.

Use the REST API to create, modify, and delete releases and release assets.

Use the REST API to manage pull requests and pull request reviews.

Use the REST API to view global security advisories.

Equivalent to the appropriate `llvm.memset.p0i8.*` intrinsic, with a size of `count * size_of::<T>()` and an alignment of `align_of::<T>()`.

Like `transmute`, but even less checked at compile-time: rather than giving an error for `size_of::<Src>() != size_of::<Dst>()`, it’s Undefined Behavior at runtime.

Use the REST API to manage blocked users.