AIStor supports publishing bucket notification events to a Kafka service endpoint. AIStor relies on the https://github.com/Shopify/sarama project for Kafka connectivity and shares that project’s Kafka support. See the sarama Compatibility and API stability section for more details. Prerequisites Kafka minimum versions and supported versions.

The AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). The batch jobs run directly on the AIStor deployment to take advantage of the server-side processing power without constraints of the local machine where you run the AIStor Client. The replicate batch job replicates objects from one AIStor deployment (the source deployment) to another AIStor deployment (the target deployment). The deployment specified as the alias becomes the ’local’ deployment for the purposes of replication.

This page documents the steps necessary to initialize site replication between two AIStor deployments. The procedures assume at least two existing AIStor installations. Only one of the two sites can have any data at the time of setup. All other sites must be empty of buckets and objects. All sites must otherwise having the following matching configurations: AIStor Server version Key Management Server for Server-Side Encryption Identity Manager Ensure each peer site has a Load Balancer, Reverse Proxy, or similar network control plane component to handle routing connections to its AIStor Server nodes. Using a single node hostname for a peer site creates a single point of failure for site replication where replication can fail if that single node goes down.

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.

This tutorial shows how to setup a KES server that uses a Thales CipherTrust Manager instance (formerly known as Gemalto KeySecure) as a persistent and secure key store. K E S C l i e n t K E S S e r v e r C i p h e r T r u s t M a n a g e r This guide assumes that you have a running CipherTrust Manager instance. It has been tested with CipherTrust Manager k170v version 2.0.0 and Gemalto KeySecure k170v version 1.9.1 and 1.10.0.

The AIStor Security Token Service (STS) AssumeRoleWithCustomToken API endpoint generates a token for use with the AIStor External Identity Management Plugin. Request endpoint The AssumeRoleWithCustomToken endpoint has the following form: POST https://aistor.example.net?Action=AssumeRoleWithCustomToken[&ARGS] The following example uses all supported arguments. Replace the aistor.example.net hostname with the appropriate URL for your AIStor cluster:

AIStor’s Object Lambda enables developers to programmatically transform objects on demand. You can transform objects as needed for your use case, such as redacting personally identifiable information (PII), enriching data with information from other sources, or converting between formats. Overview An Object Lambda handler is a small code module that transforms the contents of an object and returns the results. Like Amazon S3 Object Lambda functions, you trigger an AIStor Object Lambda handler function with a GET request from an application. The handler retrieves the requested object from AIStor, transforms it, and returns the modified data back to AIStor to send to the original application. The original object remains unchanged.

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

Reference

MinIO Key Encryption Service This site provides information about MinIO ’s Key Encryption Service (KES) project. The ...