[nycbug-talk] Off topic: S3 backups

[Brian Gupta]

It's not a library issue. You MUST in all cases delete all the
contained objects first. If you have versioning turned on, deleting
the old versions requires that you go out of your way to "delete
everything", so it's unlikely that you would accidentally delete the
bucket. That said, if you want to be extra safe, and you are willing
to put a bit of time into it, you should be able to create the access
restrictions you desire through a combination of S3 ACLs and AWS IAM
(Identity and Access Management) See the following for more details:
http://aws.amazon.com/iam/ and
http://docs.amazonwebservices.com/AmazonS3/latest/dev/index.html?UsingIAMPolicies.html

- Brian Gupta

New York City user groups calendar:
http://nyc.brandorr.com/


On Thu, Jul 29, 2010 at 12:11 PM, Matthew Terenzio <matt at thehour.com> wrote:
>
>
>
> On 7/29/10 12:00 PM, "matt at atopia.net" <matt at atopia.net> wrote:
>
>> but does that stop someone from logging in and accidentally deleting the
>> bucket? :)
>
> I believe all objects in a bucket must be deleted before a bucket can be
> deleted. At least with the library I use to work with the API.
>
>
>
>
> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org/mailman/listinfo/talk
>