Syntax Example The following command lists all anonymous links for the mydata bucket on the myaistor AIStor deployment: mc anonymous links myaistor/mydata Syntax The command has the following syntax:

Initialize MinIO client object MinIO IMinioClient minioClient = new MinioClient() .WithEndpoint("play.min.io") .WithCredentials("Q3AM3UQ867SPQQA43P2F", "zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG") .WithSSL() .Build(); AWS S3 IIMinioClient minioClient = new MinioClient() .WithEndpoint("s3.amazonaws.com") .WithCredentials("YOUR-ACCESSKEYID", "YOUR-SECRETACCESSKEY") .WithSSL() .Build(); Bucket operations Object operations Presigned operations Bucket Policy Operations makeBucket getObject presignedGetObject getBucketPolicy listBuckets putObject presignedPutObject setBucketPolicy bucketExists copyObject presignedPostPolicy setBucketNotification removeBucket statObject getBucketNotification listObjects removeObject removeAllBucketNotification listIncompleteUploads removeObjects listenBucketNotifications selectObjectContent setVersioning setLegalHold getVersioning getLegalHold setBucketEncryption setObjectTags getBucketEncryption getObjectTags removeBucketEncryption removeObjectTags setBucketTags setObjectRetention getBucketTags getObjectRetention removeBucketTags clearObjectRetention setObjectLock removeIncompleteUpload getObjectLock removeObjectLock setBucketLifecycle getBucketLifecycle removeBucketLifecycle setBucketReplication getBucketReplication removeBucketReplication 1. Constructors

This page documents settings for enabling external identity management using an OpenID Connect (OIDC)-compatible provider. See OpenID Connect Access Management 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.

Initialize MinIO client object MinIO package main import ( "log" "github.com/minio/minio-go/v7" "github.com/minio/minio-go/v7/pkg/credentials" ) func main() { endpoint := "play.min.io" accessKeyID := "Q3AM3UQ867SPQQA43P2F" secretAccessKey := "zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG" useSSL := true // Initialize minio client object. minioClient, err := minio.New(endpoint, &minio.Options{ Creds: credentials.NewStaticV4(accessKeyID, secretAccessKey, ""), Secure: useSSL, }) if err != nil { log.Fatalln(err) } log.Printf("%#v\n", minioClient) // minioClient is now setup } AWS S3 package main import ( "fmt" "github.com/minio/minio-go/v7" "github.com/minio/minio-go/v7/pkg/credentials" ) func main() { // Initialize minio client object. s3Client, err := minio.New("s3.amazonaws.com", &minio.Options{ Creds: credentials.NewStaticV4("YOUR-ACCESSKEYID", "YOUR-SECRETACCESSKEY", ""), Secure: true, }) if err != nil { fmt.Println(err) return } } Bucket operations Object operations Presigned operations Bucket Policy/Notification Operations Client custom settings MakeBucket AppendObject PresignedGetObject SetBucketPolicy SetAppInfo GetObject PresignedPutObject GetBucketPolicy ListBuckets PutObject PresignedHeadObject SetBucketNotification TraceOn BucketExists CopyObject PresignedPostPolicy GetBucketNotification TraceOff RemoveBucket StatObject RemoveAllBucketNotification SetS3TransferAccelerate ListObjects RemoveObject ListenBucketNotification RemoveObjects SetBucketLifecycle ListIncompleteUploads RemoveIncompleteUpload GetBucketLifecycle SetBucketTagging FPutObject SetObjectLockConfig GetBucketTagging FGetObject GetObjectLockConfig RemoveBucketTagging ComposeObject EnableVersioning SetBucketReplication DisableVersioning GetBucketReplication PutObjectRetention GetBucketEncryption RemoveBucketReplication GetObjectRetention RemoveBucketEncryption CancelBucketReplicationResync PutObjectLegalHold GetObjectLegalHold SelectObjectContent PutObjectTagging GetObjectTagging RemoveObjectTagging RestoreObject GetObjectAttributes 1. Constructor

The procedure on this page resynchronizes the contents of an AIStor bucket using a healthy replication remote. Resynchronization supports recovery after partial or total loss of data on an AIStor deployment in a replica configuration. For example, consider an AIStor active-active replication configuration similar to the following: Resynchronization allows using the healthy data on one of the participating AIStor deployments as the source for rebuilding the other deployment.

You can manage human and application users for your AIStor deployment with either the mc command-line tool or the AIStor console. You create these users and assign policies to them. You can also create groups of users to assign policies to. See Identity and Access Management. This page explains how to work with the built-in AIStor identity management solution. You can integrate with other identity management solutions: OpenID Connect (OIDC)

The AIStor Access Management Plugin provides a REST interface for offloading authorization through a webhook service. AIStor sends the request and credential details for every API call to the configured external HTTP(S) endpoint and looks for a response of ALLOW or DENY. AIStor can therefore delegate the access management to the external system instead of relying on S3 policy based access control. Configuration settings You can configure the AIStor External Access Management Plugin using the following environment variables or configuration settings.

Use AIStor Object Lifecycle Management to create rules for time or date based automatic transition or expiry of objects. For object transition, AIStor automatically moves the object to a configured remote storage tier. For object expiry, AIStor automatically deletes the object. AIStor derives its behavior and syntax from S3 lifecycle for compatibility in migrating workloads and lifecycle rules from S3 to AIStor. For example, you can export S3 lifecycle management rules and import them into AIStor or vice-versa. AIStor uses JSON to describe lifecycle management rules and may require conversion to or from XML as part of importing S3 lifecycle rules.

The procedure on this page creates a new object lifecycle management rule that transition objects from an AIStor bucket to a remote storage tier on the Google Cloud Storage (GCS) backend. This procedure supports use cases like moving aged data to low-cost public cloud storage solutions after a certain time period or calendar date. Requirements Install and configure mc This procedure uses mc for performing operations on the AIStor cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.

AIStor implements Transport Layer Security (TLS) 1.2+ encryption with support for Server Name Indication (SNI) for selecting relevant TLS certificates in response to client requests. You must set up TLS before you can enable data encryption, also called server-side encryption. See Configure TLS Network Encryption for how to do it on .deb or .rpm based Linux distributions. AIStor supports the following types of certificate signatures: self-signed internal or private certificate authorities (CAs)