Bucket names must be unique like domain names

  • Resolved parakeet

    (@parakeet)


    1 year, 10 months ago

    I created a new free AWS account.

    I followed the instructions at https://deliciousbrains.com/wp-offload-media/doc/amazon-s3-quick-start-guide/ …

    * Created an IAM user.
    * Applied AmazonS3FullAccess
    * Copied access key strings, inserted the relevant code into the relevant place in wp-config.php
    * In the plugin settings, elected to Create New Bucket

    I was met with Error saving bucket — Error Getting Bucket Region —There was an error attempting to get the region of the bucket {{BUCKETNAME}}: Access Denied etc etc

    On that page, all the plugin options were visible below the warning/notice.

    debug.log was not logging at this point. Then I switched it on.

    Tried again and got the same message. I checked my AWS console, and no buckets had been created.

    I came back to the plugin and tried again but got a message about BucketAlreadyExists.

    None of this was logged to debug.log.

    Process of elimination – bucket names must be unique on a global basis as they appear in the full domain URL.

    Lesson learned.

    When I used a name unique globally, the bucket could be created and new-image uploads are now flowing.

    Either I’m not yet schooled enough in the ways of AWS, or maybe this could have done with a clarification upfront in the doc?

Viewing 1 replies (of 1 total)
  • Plugin Author Delicious Brains

    (@deliciousbrains)

    1 year, 10 months ago

    That’s correct, AWS S3 uses a global namespace for bucket names as they can be addressed without knowing the region they are in etc. This global namespace is across accounts, someone else can nab a name before you and you’ll have to use something else instead.

    It’s different for DigitalOcean Spaces for example, they require every interaction to include the region, and buckets are only required to be unique for that region.

    I’ll pass on your comments about mentioning this in the docs, but we should maybe also catch that BucketAlreadyExists error and display a clearer notice that links to the doc too.

    -IJ

Viewing 1 replies (of 1 total)
  • The topic ‘Bucket names must be unique like domain names’ is closed to new replies.