Supported REST API Actions

Following, you can find REST API actions that you can use with the Snowball.

Supported REST API Actions for Snowball

HEAD Snowball

Description

Currently, there's only one Snowball REST API operation, which can be used to return status information for a specific device. This operation returns the status of a Snowball. This status includes information that can be used by AWS Support for troubleshooting purposes.

You can't use this operation with the AWS SDKs or the AWS CLI. We recommend that you use curl or an HTTP client. The request doesn't need to be signed for this operation.

Request

In the below example, the IP address for the Snowball is 192.0.2.0. Replace this value with the IP address of your actual device.

curl -X HEAD http://192.0.2.0:8080

Response

<Status xsi:schemaLocation="http://s3.amazonaws.com/doc/2006-03-01/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <snowballIp>127.0.0.1</snowballIp>
    <snowballPort>8080</snowballPort>
    <snowballId>device-id</snowballId>
    <totalSpaceInBytes>499055067136</totalSpaceInBytes>
    <freeSpaceInBytes>108367699968</freeSpaceInBytes>
    <jobId>job-id</jobId>
    <snowballServerVersion>1.0.1</snowballServerVersion>
    <snowballServerBuild>DevBuild</snowballServerBuild>
    <snowballClientVersion>Version 1.0</snowballClientVersion>
    <snowballRoundTripLatencyInMillis>33</snowballRoundTripLatencyInMillis>
</Status>

Supported REST API Actions for Amazon S3

Following, you can find the list of Amazon S3 REST API actions that are supported for using the Amazon S3 Adapter for Snowball. The list includes 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. All responses coming back from a Snowball declare Server as 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 1 – In this implementation of the GET operation, the following is true:

  • Pagination is not supported.

  • Markers are not supported.

  • Delimiters are not supported.

  • When the list is returned, the list is not sorted.

  • Only version 1 is supported. GET Bucket (List Objects) Version 2 is not supported.

  • The Snowball adapter is not optimized for large list operations. For example, you might have a case with over a million objects per folder where you want to list the objects after you transfer them to the device. In this type of case, we recommend that you order a Snowball Edge for your job instead.

• GET Service

• HEAD Bucket

• HEAD Object

• 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.

• DELETE Object

• Initiate Multipart Upload – In this implementation, initiating a multipart upload request for an object already on the Snowball first deletes that object and then copies it in parts to the Snowball.

• List Multipart Uploads

• Upload Part

• Complete Multipart Upload

• Abort Multipart Upload

Note

Any Amazon S3 REST API actions not listed here are not supported. Using any unsupported REST API actions with your Snowball Edge returns an error message saying that the action is not supported.