Release notes in S3

2026

June

added the ability to manage object and bucket locks via the control panel, for details, see the Object Lock and Manage object lock instructions;
added a new multi-AZ pool for data storage — ru-6;
added new events to audit logs: s3.bucket_object_lock.enable and s3.bucket_object_lock.update;
added the ability to connect S3 to other products over a private network via a global router, for details, see the Connect S3 to other products instructions.

April

extended CopyObject operations in conditional requests.

Now, in these operations, you can use the headers If-Match and If-None-Match. Added corresponding keys to access policies: s3:if-match and s3:if-none-match.

March

added S3 support to audit logs — s3 service;
added the ability to configure Object Lock in a bucket and lock objects;
added new roles s3.admin and s3.user.

Their capabilities are identical to those of the object_storage:admin and object_storage_user roles. You cannot assign the object_storage:admin and object_storage_user roles to new users. Users who already have these roles assigned will continue to work.

December

added consumption details by bucket.

Starting December 1, 2025, you can view the consumption of each bucket, for details, see the View consumption subsection of the S3 payment model and prices instructions;
added the ability to import a bucket policy from another bucket.

You can import a policy from other regions and pools. Rules are transferred in full, including the list of users, actions, conditions, and resources. For resources, the name of the imported bucket is automatically replaced with the name of the target bucket.

November

added a new storage class — Glacier.

Glacier storage is best suited for long-term data storage. Glacier storage is available only in the ru-3 pool.
You can view the usage cost in my.selectel.ru. For details about Glacier storage, see the Storage classes subsection of the S3 payment model and prices instructions;
added a new pool for data storage — ru-3.