On Wed, Mar 27, 2013 at 9:32 PM, Lorieri <lorieri@xxxxxxxxx> wrote: > great! > I will try this. > Will it affect objects later put through S3 api ? Yes. It sets a flag on the bucket, and reads through the S3 api will be the same as through the Swift api. It's just not possible to set that flag via the S3 api. Yehuda > > > On Wed, Mar 27, 2013 at 11:12 PM, Yehuda Sadeh <yehuda@xxxxxxxxxxx> wrote: >> >> On Wed, Mar 27, 2013 at 4:03 PM, Lorieri <lorieri@xxxxxxxxx> wrote: >> > Hi, >> > >> > There is a behavior in AWS S3 I could not reproduce in radosgw. >> > >> > If you create an empty bucket and makes it public, any object you put >> > there will be public too, and will automatically be possible to access >> > it by its http url. >> > It is very helpful when people use some tools and browsers plugins to >> > upload content or do a bulk sync. >> > >> > am I missing something ? >> >> The S3 ACLs don't allow that. Amazon provides a different orthogonal >> scheme (bucket policies) that we don't support and that makes it >> possible. >> With the rados gateway you can achieve that if you're using the swift >> api and setting the bucket public through it. >> >> >> Yehuda > > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
