This page documents the installation of the AIStor Key Encryption Service. You may require root or sudo permissions to perform some of the steps. Install the AIStor KES binary on each node in your KES cluster. Linux AMD64 curl --progress-bar --retry 10 -L https://dl.min.io/aistor/kes/release/linux-amd64/kes -o kes chmod +x ./kes mv ./kes /usr/local/bin/kes kes --version ARM64

This procedure provides guidance for enabling Server-Side Encryption (SSE) using AIStor Key Manager as the Key Management Service (KMS). Enabling SSE on an AIStor deployment automatically encrypts the backend data for that deployment using the default encryption key selected during the setup process.

This page reflects limits and thresholds that apply to AIStor Server. S3 API limits Item Specification Maximum object size 50 TiB Minimum object size 0 B Maximum object size per PUT operation 5 TiB for non-multipart upload50 TiB for multipart upload Maximum number of parts per upload 10,000 Part size range 5 MiB to 5 GiB. Last part can be 0 B to 5 GiB Maximum number of parts returned per list parts request 10,000 Maximum number of objects returned per list objects request 1,000 Maximum number of multipart uploads returned per list multipart uploads request 1,000 Maximum length for bucket names 63 Maximum length for object names 1024 Maximum length for each / separated segment of an object name 255 Maximum number of object versions for a unique object 10000 (Configurable) Erasure code limits Item Specification Maximum number of servers per cluster no limit Minimum number of servers 1 Minimum number of drives per server when server count is 1 1 (for deployments, which do not provide additional reliability or availability) Minimum number of drives per server when server count is 2 or more 1 Maximum number of drives per server no limit Read quorum $$N/2$$ Write quorum $$(N/2)+1$$ Object name limitations Filesystem and operating system restrictions Object names in AIStor are restricted primarily by the local operating system and filesystem. Windows and some other operating systems restrict file systems with certain special characters, such as ^, *, |, \, /, &, ", or ;.

Networking has the greatest impact on AIStor Server performance. Low per-host bandwidth artificially constrains the potential performance of the storage. MinIO recommends high speed networking to support the maximum possible throughput of the attached storage (aggregated drives, storage controllers, and PCIe busses). For best performance, use 100GbE or higher networking infrastructure. The following table provides a general guideline for the maximum storage throughput supported by a given physical or virtual network interface. This table assumes all network infrastructure components, such as routers, switches, and physical cabling, also supports the NIC bandwidth.

The MinIO Rust SDK is a Simple Storage Service (aka S3) client for performing bucket and object operations to any Amazon S3 compatible object storage service. It provides a strongly-typed, async-first interface to the MinIO and Amazon S3-compatible object storage APIs. Each supported S3 operation has a corresponding request builder (for example: [BucketExists], [PutObject], [UploadPartCopy]), which allows users to configure request parameters using a fluent builder pattern. All request builders implement the [S3Api] trait, which provides the async send method to execute the request and return a typed response.

The AIStor Security Token Service (STS) AssumeRoleWithLDAPIdentity API endpoint generates temporary access credentials using Active Directory or LDAP user credentials. This page documents the AIStor Server AssumeRoleWithLDAPIdentity endpoint. For instructions on implementing STS using an S3-compatible SDK, defer to the documentation for that SDK. The AIStor STS AssumeRoleWithLDAPIdentity API endpoint is modeled after the AWS AssumeRoleWithWebIdentity endpoint and shares certain request/response elements. This page documents the AIStor-specific syntax and links out to the AWS reference for all shared elements.

Create MinIO client MinIO MinioClient minioClient = MinioClient.builder() .endpoint("https://play.min.io") .credentials("Q3AM3UQ867SPQQA43P2F", "zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG") .build(); AWS S3 MinioClient minioClient = MinioClient.builder() .endpoint("https://s3.amazonaws.com") .credentials("YOUR-ACCESSKEYID", "YOUR-SECRETACCESSKEY") .build(); Bucket operations Object operations bucketExists composeObject deleteBucketCors copyObject deleteBucketEncryption deleteObjectTags deleteBucketLifecycle disableObjectLegalHold deleteBucketNotification downloadObject deleteBucketPolicy enableObjectLegalHold deleteBucketReplication getObject deleteBucketTags getObjectAcl deleteObjectLockConfiguration getObjectAttributes getBucketCors getObjectRetention getBucketEncryption getObjectTags getBucketLifecycle getPresignedObjectUrl getBucketNotification getPresignedPostFormData getBucketPolicy isObjectLegalHoldEnabled getBucketReplication listObjects getBucketTags promptObject getBucketVersioning putObject getObjectLockConfiguration putObjectFanOut listBuckets removeObject listenBucketNotification removeObjects makeBucket restoreObject removeBucket selectObjectContent setBucketCors setObjectRetention setBucketEncryption setObjectTags setBucketLifecycle statObject setBucketNotification uploadObject setBucketPolicy uploadSnowballObjects setBucketReplication setBucketTags setBucketVersioning setObjectLockConfiguration 1. MinIO Client Builder MinIO Client Builder is used to create MinIO client. Builder has below methods to accept arguments.

Memory primarily constrains the number of concurrent simultaneous connections per node. MinIO recommends at least 256GiB of RAM per host. AIStor allocates up to 75% of host memory to support GET operations. Ensure you size your host memory such that the remaining available host memory supports your target number of concurrent connections per host. You can calculate the maximum number of concurrent requests per node with this formula: $$(0.75 * totalRam) / ramPerRequest$$ramPerRequest is typically 2MiB, which is two times the default erasure block size. For questions about adjusting the erasure block size for your use case, create a SUBNET issue to discuss with MinIO engineers.

The mc update command automatically updates the mc binary to the latest stable version. Running this command is equivalent to manually downloading the latest stable binary and using it to replace the existing mc installation on the host machine. Syntax Example The following command updates the mc binary on the local host:

The MinIO Haskell Client SDK provides simple APIs to access MinIO and any Amazon S3 compatible object storage. This guide assumes that you have a working Haskell development environment. Installation Add to your project Simply add minio-hs to your project’s .cabal dependencies section or if you are using hpack, to your package.yaml file as usual.