Functional definition

evroc Object Storage provides an efficient and robust storage service for storing unstructured data such as files, videos, or backups. The service is accessible via an S3-compatible API, making it easy to integrate with existing programs already using object storage.

Features and concepts of the Object Storage service are described below.

Buckets

Buckets are containers for storing objects. Buckets are top-level containers for organizing different sets of data, e.g., for different applications.

Buckets are given names to identify them in the Console and in API calls. Bucket names must be unique within the project that they're created. Bucket names must also comply with DNS naming conventions:

• The bucket name must be between 3 and 63 characters.
• The bucket name must only consist of alphanumeric characters (a-z, A-Z, 0-9), periods (.), and hyphens (-).
• The bucket name must start and end with a lowercase alphanumeric character (a-z, 0-9).

There's a maximum limit of 1000 buckets per project. For more details on usage limits, see usage limits.

evroc wants to ensure that you don't accidentally delete any of your potentially important data. evroc therefore adds some extra checks before you can delete your bucket. For more information, see bucket deletion.

Objects

Objects are entities stored inside a bucket. Each object stores its primary data along with additional metadata about the object.

Each object is identified by a key. The key must be unique within the bucket the object is contained in.

The object consists of data, which can be used to store anything from text files to videos. The data within a single object can be up to 5 TB in size when using multipart uploads.

In addition to data, objects can also store metadata, which consists of key-value pairs. The metadata can be used to provide additional information about the object and its data, such as the content type of the data or the object's owner.

Object versioning

A bucket can be configured to enable versioning. A bucket with versioning enabled stores multiple versions of an object instead of overwriting it. This can be used to protect against accidental deletions or overwrites, ensuring that the previous version of any object can still be accessed.

Object locking

A bucket can be configured to enable object locking, in which objects can be configured with a lock to prevent them from being deleted or overwritten. This lock can be held over a configured time window.

Multipart upload

Larger uploads to an object can be broken up into separate parts, where each part can be uploaded independently and in parallel. This can speed up uploads of larger files. Each individual part can be up to 5 GB in size, for a total of 5 TB per complete object.

S3-compatible credentials

It's possible to export static credentials for accessing objects in a bucket from any S3-compatible client. This enables the Object Storage service to work with existing services or programs that integrate with S3-compatible storage.