Object tiering is the moving of the data of an object from one set of hardware to another set of hardware. This is often done as a cost-saving measure, keeping more expensive and performant hardware for the newest or most accessed objects while placing other objects to less expensive and less performant storage solutions. Retrieve a tiered object When AIStor moves an object to another tier, the object’s metadata remains on the primary tier while the object’s data moves to the secondary tier. When AIStor needs to serve a tiered object, it transparently retrieves the object from the secondary tier.

An object is binary data, such as images, audio files, spreadsheets, or even binary executable code. The term “Binary Large Object” or “blob” is sometimes associated to object storage, although blobs can be anywhere from a few bytes to several terabytes in size. Object Storage platforms like AIStor provide dedicated tools and capabilities for storing, listing, and retrieving objects using a standard S3-compatible API. AIStor Object Storage uses buckets to organize objects. A bucket is similar to a top-level drive, folder, or directory in a filesystem (/mnt/data or C:\), where each bucket can hold an arbitrary number of objects.

AIStor supports configuring a single Active Directory or LDAP (AD/LDAP) service for external management of user identities. Steps to integrate your AD/LDAP service: Configure your AIStor cluster for AD/LDAP integration. Access the AIStor console with AD/LDAP credentials. Generate temporary credentials for application access with the AssumeRoleWithLDAPIdentity Security Token Service (STS) API See the documentation for your AD/LDAP provider for detailed information about configuring user identities. Prerequisites Access to AIStor Cluster

AIStor server-side bucket replication is an automatic bucket-level configuration that synchronizes objects between a source and destination bucket. AIStor server-side replication requires the source and destination bucket be two separate AIStor clusters running the same Object Store version. For each write operation to the bucket, AIStor checks all configured replication rules for the bucket and applies the matching rule with highest configured priority. AIStor synchronizes new objects and object mutations, such as new object versions or changes to object metadata. This includes metadata operations such as enabling or modifying object locking or retention settings.

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.

The mc retention command configures the Write-Once Read-Many (WORM) locking settings for an object or object(s) in a bucket. You can also set the default object lock settings for a bucket, where all objects without explicit object lock settings inherit the bucket default. Subcommands mc retention includes the following subcommands:

mc support upload copies a file from the local file system to a SUBNET ticket. Syntax The command has the following syntax: mc [GLOBALFLAGS] support profile \ ALIAS \ FILE \ [--comment "string"] \ [--enc] \ [--issue integer] Parameters ALIAS Required

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:

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.

Warp Documentation Warp is an open-source testing tool for S3-compatible object storage systems. Use Warp to evaluate...