Changelog

S3 storage service changelog

[May 19, 2018 - v.7.0.2]

* Added support for auto-tiering to the following destinations :

Amazon AWS S3
Amazon AWS Glacier
Microsoft Azure
Google Cloud Storage
Spectra Logic BlackPearl

Notes:

By default the largest object size that can be auto-tiered to Amazon, Google, or other S3-compliant destinations is 50GB. This
50GB limit does not apply to tiering to Azure or Spectra BlackPearl.

Tiering to Azure or Spectra BlackPearl is not supported for source buckets that have versioning enabled or that have had versioning enabled in the past.

When auto-tiering to Spectra BlackPearl is used for a bucket, objects in the bucket will not be autotiered unless they are larger than 5MB. Objects 5MB or smaller will remain stored inside their source bucket. 

* Support for downloading objects via BitTorrent

The S3 Service now supports the S3 API method GET Object torrent, for using BitTorrent to download objects. The CMC's S3 client does not support the GET Object torrent method. However, the S3 Service supports this method if called by a third party S3 client application. This feature allows to reduce traffic for popular objects by supporting distribution through peer-to-peer Torrent protocol that lessen accesses to the original object. More information

* Support for object tagging

The S3 Service now supports the S3 API methods and headers that enable S3 client applications to assign user defined object tags to new objects as they're being uploaded or to objects already stored. Object tags are key-value pairs that can be used to describe or classify objects, such as project=apollo or statuss=needs-review.

* Support for WORM policies per bucket

The S3 service now supports applying a "Write Once, Read Many" (WORM) policy to a bucket, so that data in a bucket is kept in unaltered form for a defined retention period. This is implemented as a set of extensions to the S3 API.