Release notes in S3

2026

June

added new events to audit logs: s3.bucket_object_lock.enable and s3.bucket_object_lock.update.

April

expanded CopyObject operations in conditional requests.

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

March

added S3 support in audit logs — s3 service;
added the ability to configure Object Lock for buckets 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 have already been assigned these roles will continue to work.

December

added consumption details per 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 instruction;
added the ability to import an access policy from another bucket.

You can import policies from other regions and pools. Rules are transferred in their entirety, 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 usage costs at my.selectel.ru. Read more about cold storage in the Storage classes subsection of the S3 Payment model and prices instruction;
added a new pool for data storage — ru-3.