Supported Amazon S3 REST API Actions
Following, you can find the list of Amazon S3 REST API actions that are supported for using
the Amazon S3 Adapter for Snowball, with links to information about how the API actions work with Amazon S3. The
list also covers any differences in behavior between the Amazon S3 API action and the Snowball
counterpart. Note that all responses coming back from a Snowball declare
AWSSnowball, as in the following example.
HTTP/1.1 200 OK x-amz-id-2: JuKZqmXuiwFeDQxhD7M8KtsKobSzWA1QEjLbTMTagkKdBX2z7Il/jGhDeJ3j6s80 x-amz-request-id: 32FE2CEB32F5EE25 Date: Fri, 08 2016 21:34:56 GMT Server: AWSSnowball
GET Bucket (List Objects) Version 2 – In this implementation of the GET operation, prefixes are partially supported but delimiters are not. If the prefix is a directory on the Snowball, this operation lists objects and directories within that directory, if the exact prefix is used. For example, if you have a directory called flowers on a Snowball, and you specify the prefix as
flower, nothing within the flowers directory will return.
GET Object – When an object is uploaded to a Snowball using
GET Object, an entity tag (ETag) is not generated unless the object was uploaded using multipart upload. The ETag is a hash of the object. The ETag reflects changes only to the contents of an object, not its metadata. The ETag might or might not be an MD5 digest of the object data. For more information on ETags, see Common Response Headers in the Amazon Simple Storage Service API Reference.
PUT Object – When an object is uploaded to a Snowball using
PUT Object, an ETag is not generated unless the object was uploaded using multipart upload.
Initiate Multipart Upload – In this implementation, initiating a multipart upload request for an object already on the Snowball will first delete that object and then copy it in parts to the Snowball.