tag:blogger.com,1999:blog-3922219755971684412.post1491849378308355099..comments2023-07-12T06:28:09.649-04:00Comments on Decoded Node: Renaming buckets on S3Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3922219755971684412.post-85347504778543330512015-10-12T15:29:31.947-04:002015-10-12T15:29:31.947-04:00AFAIK, that's an inherent limitation of S3'...AFAIK, that's an inherent limitation of S3's design. It's going to take a lot of requests no matter how you slice it, as long as the API doesn't have a native "rename bucket" operation.sapphirepawhttps://www.blogger.com/profile/08959423651720108923noreply@blogger.comtag:blogger.com,1999:blog-3922219755971684412.post-10518589123838892272015-10-03T13:31:45.836-04:002015-10-03T13:31:45.836-04:00Note that the console is written in Javascript, an...Note that the console is written in Javascript, and so it works by your browser sending per-file requests to S3. So you will have to wait for your browser to send one http request per file you are copying. You will also incur a charge of one thousandth of a cent (at today's rates) for each of these requests.<br /><br />So: this approach works, but if there are a million objects in the bucket, it will take between hours to days, and cost ten dollars.Anonymousnoreply@blogger.com