AIStor Server uses the built-in scanner to check objects for healing and to take any scheduled object actions. Such actions may include: calculate data usage on drives evaluate and apply configured lifecycle management or object retention rules perform bucket or site replication check objects for missing or corrupted data or parity shards and perform healing The scanner performs these functions at two levels: cluster and bucket. At the cluster level, the scanner splits all buckets into groups and scans one group of buckets at a time. The scanner starts with any new buckets added since the last scan, then randomizes the scanning of other buckets. The scanner completes checks on all bucket groups before starting over with a new set of scans.

The AdminJob Custom Resource Definition (CRD) allows administrators to run AIStor Client (mc) commands against an AIStor cluster using declarative Kubernetes YAML configurations. Each command runs in a Kubernetes Job pod that is authenticated with the specified ServiceAccount and STS credentials. Prerequisites Kubernetes ServiceAccount with PolicyBinding - Create a ServiceAccount and bind it to appropriate policies using the PolicyBinding CRD. The ServiceAccount provides the identity, while the PolicyBinding grants permissions. Existing AIStor Object Store deployment - AdminJob targets an existing ObjectStore cluster. Quick start This minimal example uses AdminJob to create a bucket named my-bucket in the primary-object-store cluster using the consoleAdmin policy for full administrative access. Save the following YAML as adminjob-quickstart.yaml to get started:

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.

This page documents settings for configuring Security Token Service (STS) behavior in AIStor. STS provides temporary security credentials for users authenticated through external identity providers such as OpenID Connect or LDAP. You can establish or modify these settings by defining environment variables 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. These settings are environment variables only and do not have corresponding mc admin config settings.

Initialize MinIO client object MinIO import * as Minio from 'minio' const minioClient = new Minio.Client({ endPoint: 'play.min.io', port: 9000, useSSL: true, accessKey: 'Q3AM3UQ867SPQQA43P2F', secretKey: 'zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG', }) AWS S3 import * as Minio from 'minio' const s3Client = new Minio.Client({ endPoint: 's3.amazonaws.com', accessKey: 'YOUR-ACCESSKEYID', secretKey: 'YOUR-SECRETACCESSKEY', }) Bucket operations Object operations Presigned operations Bucket Policy & Notification operations Custom Settings makeBucket getObject presignedUrl getBucketNotification setS3TransferAccelerate listBuckets getPartialObject presignedGetObject setBucketNotification bucketExists fGetObject presignedPutObject removeAllBucketNotification removeBucket putObject presignedPostPolicy getBucketPolicy listObjects fPutObject setBucketPolicy listObjectsV2 copyObject listenBucketNotification listIncompleteUploads statObject getBucketVersioning removeObject setBucketVersioning removeObjects getBucketTagging removeIncompleteUpload setBucketTagging putObjectRetention removeBucketTagging getObjectRetention setBucketLifecycle setObjectTagging getBucketLifecycle removeObjectTagging removeBucketLifecycle getObjectTagging setObjectLockConfig getObjectLegalHold getObjectLockConfig setObjectLegalHold getBucketEncryption composeObject setBucketEncryption selectObjectContent removeBucketEncryption setBucketReplication getBucketReplication removeBucketReplication 1. Constructor

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.

The AIStor Security Token Service (STS) APIs allow applications to generate temporary credentials for accessing the AIStor Server. The STS API is required for AIStor Servers configured to use external identity managers, as the API allows conversion of the external IDP credentials into AWS Signature v4-compatible credentials. STS API endpoints AIStor supports the following STS API endpoints:

This page covers settings that manage access and behavior for the batch job process. 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.

AIStor supports running in S3 Express Mode. This mode enables directory bucket behavior for optimized heirarchial storage structures. While object store prefixes generally support organized storage, S3 Express Mode implements the specific directory bucket behaviors documented by AWS. S3Express mode disables most API operations outside of simple bucket and object PUT, GET, DELETE, and LIST operations. All other API operations return not supported errors, including operations for versioning, locking, and replication.

MinIO Key Management Service This documentation provides guidance on installation, usage, and configuration of the en...