100

Title is quite explanatory, but I have just deleted an s3 bucket as it was in the wrong region and am wanting to recreate it in the correct region with same name as the just deleted one.

Is there any documentation of this or user experience?

ljs.dev
  • 1,174
  • 2
  • 8
  • 15
  • Delete bucket `A` in region `1` and recreating it in region `2`, I've had to wait as long as 45-minutes. – Adam Jul 18 '19 at 12:23
  • Many hours in my experience. You can recreate it in the console almost instantly, but the bucket is not really there. It doesn't show any access or region information and gives an error when listing the content. Same result with the CLI. My guess is that amazon runs some process every few hours that performs the needed cleanup. – Federico Sep 02 '20 at 09:39
  • 2
    "You can recreate it in the console almost instantly" -- that does not match my experience. Instead, it throws an API error like so: "A conflicting conditional operation is currently in progress against this resource. Please try again." (That was via the AWS Console, not using the CLI or one of the SDKs, I'll note.) – Morgan Blackthorne Sep 18 '20 at 18:35

3 Answers3

95

The S3 docs used to say:

When you delete a bucket, there may be a delay of up to one hour before the bucket name is available for reuse in a new region or by a new bucket owner. If you re-create the bucket in the same region or with the same bucket owner, there is no delay.

But now they just say:

... it might take some time before the name can be reused ...

Andrew Schulman
  • 8,561
  • 21
  • 31
  • 47
Greg
  • 1,353
  • 1
  • 12
  • 13
  • 5
    This information may be out of date as it's been removed from the documentation. – r3m0t Jan 20 '17 at 12:39
  • 5
    Today it took more than 1h for me. – Martin Thoma Apr 06 '18 at 15:24
  • 1
    This seems to also apply for moving buckets from one AWS account to another. – Jay Prall Dec 18 '19 at 16:43
  • If you delete a bucket and recreate it in the same region and account, it's a few seconds in general. The long wait times happen if you switch account when recreating, and maybe if you switch region in the same account. Haven't tried the latter. – mhvelplund Jul 02 '21 at 08:49
  • 1
    I'm trying to 'move' a bucket from one region to another on the same account and getting the error `A conflicting conditional operation is currently in progress against this resource. Please try again.`. I'll update how long it takes once complete. – Dean Meehan Aug 06 '21 at 15:26
  • 1
    It took me 1 hour 45 mins today. – eldos Sep 25 '21 at 15:32
  • @DeanMeehan how long did it take? Or are you still waiting? – Ian Lovejoy Mar 08 '22 at 04:29
  • 1
    @Ian It was aprox. the same as above. 1hr 45minutes. Thanks for the reminder. – Dean Meehan Mar 09 '22 at 11:37
  • It took me about an hour. Specifically, trying to create the bucket while creating a CloudFormation stack led to get the "conflicting conditional operation" error after half an hour on the first try and took another half an hour to succeed on the second try. – rrobby86 Apr 13 '22 at 11:30
16

I've had to wait 5-10 minutes at times.

ceejayoz
  • 32,469
  • 7
  • 81
  • 105
  • 7
    It's been over half an hour and I'm still waiting... – Asfand Qazi Mar 10 '16 at 08:04
  • 1
    @AsfandYarQazi OK? Contact AWS support if it's still stuck. – ceejayoz Mar 10 '16 at 14:05
  • 38
    It took over an hour. Just letting people know not to pin their hopes on it taking 10 minutes, it may take much longer. – Asfand Qazi Mar 10 '16 at 17:56
  • 1
    Took exactly an hour today. – Marc Tamsky Jun 08 '17 at 04:05
  • 4
    FYI, deleted three buckets because I wanted to move them to a different region. It took an hour for one of the names to become available after deletion. However, it took several hours for two of them to become available (they were in a sort of limbo: still showing in the list after deletion, but without region name and without any ability to try and delete them again.) So bottom-line: just be patient. – Fabien Snauwaert Aug 28 '17 at 22:28
  • 1
    yeah, bucket limbo state, having same issue, sometimes its super fast, today its already 12 hours... – kensai Nov 26 '19 at 17:29
  • 1
    Took about an hour for one bucket, and even more for another. – Mark Kahn May 15 '20 at 08:08
-5

about 5-10 seconds. Bucket names must be region-unique (you can create us-1/test and eu-1/test simultaneously). It looks like someone create bucket in region with name you want to use.

edit: Bucket name is globally unique.

Paul Rudnitskiy
  • 399
  • 2
  • 4
  • was able to create it, but more inline with the 5 to 10mins below. The string was very unique, so was not created by anyone else. – ljs.dev Nov 12 '13 at 19:04
  • 9
    This answer provides additional information that is not at all accurate. Bucket names are a single global (not regional) namespace. [*"The bucket namespace is global - just like domain names. You can't create a bucket with a name that is already used by another Amazon S3 user."*](http://aws.amazon.com/articles/Amazon-S3/1109#02) You also can't create one with the same name as one you already have in a different region. – Michael - sqlbot Nov 16 '13 at 02:33
  • "The string was very unique" - it's a binary property – Phil Mar 17 '21 at 02:34