Supported Amazon S3 features
Besides basic Amazon S3 operations like GET, PUT, COPY, DELETE, the Bamboozle Object Storage implementation of the Amazon S3 protocol supports the following features:
Multipart upload
Access control lists (ACLs)
Versioning
Signed URLs
Object locking
Geo-replication
Server access logging
Object storage classes
Cross-region replication (CRR)
Bucket policies
Object expiration
Cross-origin resource sharing (CORS)
Supported authentication schemes
The following authentication schemes are supported by the Bamboozle Object Storage implementation of the Amazon S3 protocol:
The following authentication methods are supported by the Bamboozle Object Storage implementation of the Amazon S3 protocol:
The following authentication method is not supported:
Supported Amazon request headers
The following Amazon S3 REST request headers are currently supported by the Bamboozle Object Storage implementation of the Amazon S3 protocol:
Authorization
Content-Length
Content-Type
Content-MD5
Date
Host
x-amz-content-sha256
x-amz-date
x-amz-security-token
x-amz-object-lock-retain-until-date
x-amz-object-lock-mode
x-amz-object-lock-legal-hold
x-amz-bypass-governance-retention
x-amz-bucket-object-lock-enabled
x-amz-geo-endpoint
x-amz-geo-access-key
x-amz-geo-access-secret
Supported Amazon response headers
The following Amazon S3 REST response headers are currently supported by the Bamboozle Object Storage implementation of the Amazon S3 protocol:
Content-Length
Content-Type
Connection
Date
ETag
x-amz-delete-marker
x-amz-request-id
x-amz-version-id
x-amz-object-lock-retain-until-date
x-amz-object-lock-mode
x-amz-object-lock-legal-hold
x-amz-geo-endpoint
x-amz-geo-access-key
x-amz-geo-access-secret
The following Amazon S3 REST response headers are not used:
Server
x-amz-id-2
Supported Amazon error response headers
The following Amazon S3 REST error response headers are currently supported by the Bamboozle Object Storage implementation of the Amazon S3 protocol:
Code
Error
Message
The following Amazon S3 REST error response headers are not supported:
RequestId (not used)
Resource
Supported Amazon S3 object expiration actions
The Flow Object Storage implementation of the Amazon S3 object lifecycle only supports object expiration by prefix. Deleting objects by tag is not available. The rule definition for object expiration is similar to that for bucket policies.
The following S3 object expiration actions are currently supported:
Expiration. Deletes objects by age or by date. In case of versioning, inserts a delete marker, which becomes the latest version of an object. Delete markers are not removed.
NonCurrentVersionExpiration. Deletes an object version after it has become non-current for the specified number of days.
AbortIncompleteMultipartUpload. Aborts a multipart upload that has not completed during the specified number of days.
ExpiredObjectDeleteMarker. Deletes a delete marker as soon as there are no other versions of an object.
Last updated
