The mc undo command reverses changes due to either a PUT or DELETE operation at a specified path. Syntax Example The following command reverts the last three uploads and/or deletions of the file.zip object on the myaistor deployment in the data bucket:

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 following section documents settings for configuring AIStor to publish minio server logs to an HTTP webhook endpoint. See Publish Server Logs to HTTP Webhook for more complete documentation and tutorials on using these settings. Example Environment Variables You can specify multiple webhook endpoints as log targets by appending a unique identifier _ID for each set of related logging environment variables. For example, the following settings define two distinct server log webhook endpoints:

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.

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.

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

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:

1. Constructor Minio(endpoint, access_key=None, secret_key=None, session_token=None, secure=True, region=None, http_client=None, credentials=None) Initializes a new client object.

1701

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: