4 ms·
there was a S3 sync client that some people used that did: aws s3 sync --delete ./ s3://your-bucket/ The delete flag was added by just a very innocuous ch
by VWWHFSfQ 8y ago
there was a S3 sync client that some people used that did:
aws s3 sync --delete ./ s3://your-bucket/
The delete flag was added by just a very innocuous checkbox in the UI. The result is that it removes anything not in the source directory. Kaboom. Everything's gone. The point is you have no idea what stuff is going to do even if you think it's obvious.
- PetahNZ 8y agoThis would take so many hours to actually run though, probably weeks for that amount of data.
- itronitron 8y agomaybe someone at Tumblr can test this...
- dahfizz 8y agoMaybe the moral is that you shouldn't rely on third party clients for mission critical stuff if you dont know what they do.
- VWWHFSfQ 8y agoand also have backups like a normal competent person/organization does
- foxtrottbravo 8y agoI know in the particular example that is something that's good advise and more or less easily done. Do you think it would be good to extend said argument to say scp / ftp clients?
- bashinator 8y agoawscli is a first-party client.
- scarface74 8y agoHe mentioned a third party GUI wrapper on top of the CLI.
- electroly 8y agoHave you tried this? It takes forever to clean out a bucket. At the scale we're talking about, doing this on a single thread from the CLI tool means you could go home and come back the next day and cancel it then, and you still wouldn't have made a particularly big dent in the bucket. It's really a pain in the neck to delete a whole bucket full of data when you actually want to. It's "easy" to start off a recursive delete, sure, but I think you're overestimating the "kaboom" factor.