Object and Bucket Management Features
The VK Object Storage service supports the following capabilities for working with buckets and objects:
- standard and multipart upload of objects to a bucket;
- configuring automatic deletion of objects (lifecycle);
- copying objects;
- object deletion lock (object lock);
- notifications about bucket events;
- a set of tools for access management for buckets and objects;
- an API for programmatically managing buckets and objects using standard HTTP requests.
Files of any type can be uploaded to a bucket, for example, images, backups, videos. After upload, the file is stored as a VK Object Storage object.
Depending on the file size, different upload methods are recommended:
- Up to 1 GB — standard upload in any convenient way: via the management console, file managers, CLI, SDK, or API.
- Over 1 GB — CLI, SDK, or API.
- Over 32 GB — only multipart upload via CLI, SDK, or API.
With multipart upload, data is divided into several parts that are uploaded independently, one by one, in any order. If the transfer of any part fails, it can be retransmitted without affecting the other parts. Once all parts are uploaded, the storage assembles them together in the specified order and creates the object.
Advantages of multipart upload:
- Parts of a large file can be uploaded in parallel, thereby reducing upload time.
- If some part was not uploaded due to a network error, it is faster to re-upload it than a large file.
- The upload can be paused and resumed later.
- The upload can be started before the final file size is known, i.e. the file can be uploaded as it is being created.
VK Object Storage allows you to create copies of stored objects. Copying is performed using CLI, SDK, file manager or API.
With copying, you can:
-
Create additional copies of objects in the same or a different bucket.
-
Rename objects.
Direct renaming of objects in a bucket is not supported. You can work around this limitation by creating a copy of the object with a new name and then deleting the original object. In file managers, these actions are performed automatically.
-
Change object metadata.
When an object is uploaded to a bucket, it is assigned metadata in key/value format. The only way to change it after upload is to create a copy of the object with the same name, specifying new metadata in the copy request. This way, you can change user metadata and some system metadata, for example, the storage class.
-
Copy the tags of the source object or set new tags on the new object.
VK Object Storage allows you to configure sending notifications about bucket events using webhooks. Each webhook specifies the event type and the URL to which a message or HTTP/HTTPS request is sent when an event of the specified type occurs in the bucket. You can create webhooks for the following event types:
- object creation;
- object copying;
- object deletion;
- multipart upload completion.
Using webhooks allows you to:
- inform the user about an event that occurred in the bucket;
- configure file processing and conversion after upload;
- configure interaction with external systems;
- enable logging for object storage.
The webhook configuration for a bucket is created via the management console or using the API.
Object tagging allows you to logically group objects. Tagging is done with tags (tag). A tag is a key/value pair.
Limits:
-
For an object with a tag:
- An object can have up to 10 tags.
- Tags associated with objects must have unique keys.
-
For a tag key and value:
- Key length — up to 128 Unicode characters, but no more than 256 bytes.
- Value length — up to 256 Unicode characters, but no more than 528 bytes.
- Encoding — UTF-16.
- The key and value are case-sensitive.
- Allowed characters — Latin letters, digits, spaces, and the symbols
+,-,=,.,_,:,/.
Tags can be added to new objects upon upload or to existing objects.
VK Object Storage provides a RESTful XML API for programmatically managing buckets and objects using standard HTTP requests. The VK Object Storage API is designed to interoperate with the Amazon Web Service S3 API and has a compatible interface. Access to the VK Object Storage API uses the protocol created for the AWS S3 service.
You can send API requests via CLI, SDK, or file managers.
Some AWS S3 API methods are not implemented in the VK Object Storage service. Requests for such methods return an S3-compatible NotImplemented error response in XML format.