We provide support for another API that is becoming ubiquitous. In this case it is the Amazon S3 API. This is already used in solutions such as Eucalyptus Walrus, and we have now also added it as entry point for any files
accessed through a SMEStorage Account. This means you can use the S3 compatible API to access your files on Google Docs, or Google Storage, or RackSpace Cloud Files, or Microsoft OneDrive, or any of the many other Clouds that we support.
For those interested, moving from a file based structure to a flat file object structure was achieved using the depth first algorithm
within the implementation mapping to our API
Below is a practical implementation of using the S3 API.
Setting up an S3 Tool to work with SMEStorage
Lets look at a practical implementation of the S3 API using a tool that supports S3 compatible endpoints, CloudBerry explorer. We’ll use this to access our Google Docs / Drive, although we could have chosen DropBox, or any other number of clouds to access.
Choose to add an account and fill in the endpoint as either:
‘s3.storagemadeeasy.com’ (US Server) or
's3eu.storagemadeeasy.com' (EU Server)
and the QueryID should be set as the SME username. You can obtain the API key from logging into SME going to “My Account” from the sidebar and copying the API key from where it says “API secret Key”
You can can now browse, download, upload files directly from your SME Clouds which is happening over the S3 API.
The S3 API can be useful in a number of scenarios. For example:
- Building an S3 compatible Cloud but using one or more different Storage implementations to deliver it, using the SMEStorage Cloud Appliance.
- Transitioning from existing S3 use to a different Cloud but without having to change code ie. only changing the endpoint implementation
- Using S3 Tools and scripts to work with Clouds other than S3