AWS::S3::BucketAlreadyOwnedByYou error

[Mark Evans]

Pasted from blog comment:

...One question, though: I'm trying to use dragonfly with S3 on heroku
but I keep on getting 'AWS::S3::BucketAlreadyOwnedByYou (Your previous
request to create the named bucket succeeded and you already own
it.):'

Without any deeper knowledge of your code and only very brief look
into 'lib/dragonfly/data_storage/s3data_store.rb' I got the impression
that dragonfly tries to create the bucket every time I save an
attachment again? Am I seeing this correctly? Could there be a check
missing if the bucket already exists? Or am I somehow using it wrong?

Any hint would be greatly appreciated. — Cheers!

polarblau


--
Subscription settings: http://groups.google.com/group/dragonfly-users/subscribe?hl=en

[Mark Evans]

It should only try to create the bucket the first time it's used, and
even then, I found that if it already existed it didn't complain.

What version of the aws/s3 gem do you have?

[polarblau]

Thanks for bringing this topic over here. I'm using the version 0.6.2
of the aws-s3 gem, it's already installed at heroku.

I'm not entirely sure if I'm handling everything right (it's my first
use–case for S3, Heroku as well as dragonfly), but I tried to follow
your example usage for this combination and locally — with the common
data storage — everything works just fine.
But when I try to use it in production I'm getting the mentioned
error.

I have done both: created my bucket "manually" in advance and let
dragonfly create it. The first leads to be here described problem, the
second one causes a different error: 'AWS::S3::OperationAborted (A
conflicting conditional operation is currently in progress against
this resource. Please try again.)', which seems to point at the same
problem ( http://developer.amazonwebservices.com/connect/thread.jspa?threadID=25368#jive-message-104253
).

Any help would be greatly appreciated.

[polarblau]

After doing a lot of digging online, I found out that there's a
related problem with buckets created in Europe. After creating a
bucket in the US everything started to work fine. Is it possible to
specify in the initializer where the bucket will be situated? Or is
there a better way to resolve this problem?

[Titus Kamau]

I Have the same problem,if created from Nairobi Kenya.I created the bucket though manually and the same problem persists. The reason for error is due to the fact that amazon hasn't released/refreshed the bucket,for more details see http://awsdocs.s3.amazonaws.com/S3/latest/s3-api.pdf.Though it seams creating the bucket in us standard does not help still,any one with another way to go?is it possible to make a configuration which makes the bucket not to be recreated?