The mc support perf net command measures the network throughput of all nodes in a cluster. Use this command to identify potential network performance bottlenecks in your deployment. Syntax Example The following command runs a network throughput test on a cluster with alias myaistor.

The mc replicate update command modifies an existing bucket replication rule. Syntax Example The following command modifies an existing replication rule for the mydata bucket on the myaistor AIStor deployment:

The mc idp openid accesskey enable enables the specified access key on the local server. Example and syntax Example The following example enables the access key mykey from the myaistor deployment:

The mc ping command performs a liveness check on a specified target. Syntax Example The following sends a response request to the target(s) and outputs the minimum, maximum, average, and roundtrip times of the response, as well as the number of errors encountered when processing the request.

The mc idp openid enable command starts using an existing set of configurations for an OIDC provider with your AIStor deployment. Example and syntax Example The following example enables the server configurations defined as test_config on the myaistor deployment.

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.

Reference

This page documents environment variables for configuring AIStor to publish data to an HTTP webhook endpoint and trigger an Object Lambda function. See Transforms with Object Lambda for more complete documentation and tutorials on using these environment variables. Environment Variables You can specify multiple targets by appending a unique identifier _ID for each set of related settings.

The mc version info command returns the versioning status for the specified bucket. Syntax Example The following command returns the versioning status for the mybucket bucket on the myaistor AIStor deployment:

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 ;.