CEPH filesystem development
 help / color / mirror / Atom feed
From: Florian Haas <florian@hastexo.com>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Configuring radosgw to behave like Amazon S3
Date: Mon, 09 Jul 2012 21:50:15 +0200	[thread overview]
Message-ID: <4FFB35F7.5080807@hastexo.com> (raw)
In-Reply-To: <CAC-hyiGMrd4LVy6H5StT3SpXC6tx7ht3gooZT7mnh6bFBt05qA@mail.gmail.com>

On 07/09/12 18:39, Yehuda Sadeh wrote:
> On Mon, Jul 9, 2012 at 6:00 AM, Florian Haas <florian@hastexo.com> wrote:
>> Hi,
>>
>> I find it kind of neat that you can use radosgw to convince S3 clients
>> that they are in fact talking to the "real" Amazon S3, with just a bit
>> of config and DNS trickery, but haven't seen this documented anywhere.
>> So I decided to add a little page to the Hints & Kinks section on our
>> website, in the hope that it's useful. If anyone wants to share
>> comments, feedback or corrections, please do so either here on the
>> list, or on the page directly (scroll down to "add new comment";
>> leaving comments requires you to log in in an effort to combat comment
>> spam).
>>
>> http://www.hastexo.com/resources/hints-and-kinks/configuring-radosgw-behave-amazon-s3
> 
> Note that for obvious reasons this method can't work when accessing
> the RESTful api via https. It is useful as a workaround for handling
> clients that are hard coded for amazon.

Point taken, I've added a paragraph saying that while technically
feasible, such HTTPS hackery shouldn't be attempted.

>> As a side note, I'm not 100% sure if the information listed in
>> http://ceph.com/docs/master/radosgw/s3/ with respect to S3 API
>> compatibility is entirely accurate. Specifically, it seems that the
>> "Bucket Website" feature *is* supported by way of "rgw dns name"
>> (unless I'm missing something, and Bucket Website refers to something
>> different). Thoughts on that would also be appreciated.
> 
> Yeah, you're missing something. Bucket website is a way to configure a
> bucket to behave like a static website by providing default landing
> page when accessing the bucket's root, and by providing default error
> pages. You can read all about it here:
> 
> http://docs.amazonwebservices.com/AmazonS3/latest/dev/WebsiteHosting.html

Thanks.

Cheers,
Florian

      reply	other threads:[~2012-07-09 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 13:00 Configuring radosgw to behave like Amazon S3 Florian Haas
2012-07-09 16:39 ` Yehuda Sadeh
2012-07-09 19:50   ` Florian Haas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FFB35F7.5080807@hastexo.com \
    --to=florian@hastexo.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=yehuda@inktank.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox