[tahoe-lafs-trac-stream] [tahoe-lafs] #917: Amazon S3 compatible frontend

[tahoe-lafs]

#917: Amazon S3 compatible frontend
-------------------------------+-----------------------------------------
     Reporter:  francois       |      Owner:
         Type:  enhancement    |     Status:  new
     Priority:  minor          |  Milestone:  eventually
    Component:  code-frontend  |    Version:  1.5.0
   Resolution:                 |   Keywords:  frontend s3-frontend amazon
Launchpad Bug:                 |
-------------------------------+-----------------------------------------
Changes (by davidsarah):

 * keywords:  frontend s3 amazon => frontend s3-frontend amazon


Old description:

> Allowing existing S3 clients to access files on a Tahoe grid sounds cool.
>
> Would it be possible to build such a S3-compatible frontend for Tahoe?
> Should it be implemented as a new frontend or as a proxy between the WAPI
> and S3 clients?
>
> A few interesting references:
>
>   * [http://docs.amazonwebservices.com/AmazonS3/latest/ S3 API
> documentation]
>   * [https://launchpad.net/txaws A Twisted API for accessing Amazon Web
> Services]

New description:

 Allowing existing S3 clients to access files on a Tahoe grid sounds cool.

 Would it be possible to build such a S3-compatible frontend for Tahoe?
 Should it be implemented as a new frontend or as a proxy between the WAPI
 and S3 clients?

 A few interesting references:

   * [http://docs.amazonwebservices.com/AmazonS3/latest/ S3 API
 documentation]
   * [https://launchpad.net/txaws A Twisted API for accessing Amazon Web
 Services]

--

Comment:

 S3 clients will assume that files are accessible under specified names,
 rather than cap URIs. I'm not really sure that S3's security model is very
 compatible with Tahoe's, unless you have a file mapping (Access Key ID,
 secret key) pairs to root caps, like the SFTP and FTP frontends.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/917#comment:6>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage