Supported Operations Overview

Below is a high level overview of the Amazon AWS S3 operations supported by S3Connect

  • List buckets and folders

  • Upload objects
  • Multipart uploads
  • Download objects

  • Delete objects

  • Delete multiple objects

Unsupported Operations Overview

Below is a high level overview of the Amazon AWS S3 operations not supported by S3Connect

  • Bucket operations (except listing)
  • Versioning
  • CORS*
  • Replication (across regions)
  • Tagging
  • Using a bucket as a website
  • Acceleration
  • Location (there is no concept of regions in MatrixStore)
  • Torrents
  • Policies
  • Logging
  • Payment


* Basic CORS headers added to all responses and pre-fetch supported, however it is not possible to set CORS rules for a bucket.

Supported Operations (full list)

Below is the full list of the Amazon AWS S3 operations supported by S3Connect

Operations on the Service

  • GET Service

Operations on Buckets

  • GET Bucket (List Objects) Version 1 & 2
  • HEAD Bucket

Operations on Objects

  • Delete Multiple Objects
  • DELETE object

  • GET Object
  • HEAD Object
  • PUT Object
  • PUT Object - Copy
  • Abort Multipart Upload
  • Complete Multipart Upload
  • Initiate Multipart Upload
  • List Parts
  • Upload Part
  • Upload Part - Copy

Unsupported Operations (full list)

Below is the full list of the Amazon AWS S3 operations not supported by S3Connect

Operations on Buckets

  • All operations other than GET Bucket (List Objects) Version 1/2 and HEAD Bucket

Operations on Objects

  • DELETE Object tagging
  • GET Object ACL
  • GET Object legal hold
  • GET Object retention
  • GET Object tagging
  • GET Object torrent
  • OPTIONS object
  • POST Object
  • POST Object restore
  • PUT Object legal hold
  • PUT Object retention
  • PUT Object acl
  • PUT Object tagging
  • SELECT Object Content


 


Limitations with other MatrixStore Applications


You can combine S3 access to MatrixStore objects with other MatrixStore application as long as the objects are created by S3Connect. In that case, the objects will be visible and can be accessed by any other MatrixStore application.


Objects created by other MatrixStore applications may not be accessible through S3Connect.