AIStor supports using an OpenID Connect (OIDC) identity provider (IDP) such as Okta, KeyCloak, Dex, Google, or Facebook for external management of user identities. This page explains how to configure an OIDC provider for AIStor on Kubernetes and baremetal infrastructures. See OpenID Connect Access Management for how to set up appropriate access controls for OIDC-managed identities. This procedure is generic for OIDC compatible providers. Refer to the documentation for the OIDC provider of your choice for specific information.

Object Store 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.

Kes

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

This page documents settings for configuring a Redis service as a target for Bucket Notifications. See Publish Events to Redis for a tutorial on using these settings. 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.

The following section documents environment variables for configuring AIStor to publish audit logs to a Kafka broker. The top-level configuration key for defining a Kafka broker target for publishing AIStor audit logs. Example Environment Variables export MINIO_AUDIT_KAFKA_BROKERS="https://kafka-endpoint.example.net:9092" Configuration Settings Use mc admin config set to set or update a Kafka audit target. Specify additional optional arguments as a whitespace (" ")-delimited list.

This page documents settings for enabling external authorization management using the AIStor Access Management Plugin. See AIStor External Access Management Plugin for a tutorial on using these settings. 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 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.

AIStor Volume Manager This set of pages describes Volume Manager, a Container Storage Interface (CSI) for direct atta...

The following commands have been deprecated. Replacement commands are listed, where applicable. Deprecated Subcommands Description identity ls Use kes ls key ls Use kes ls policy ls Use kes ls