Skip to content
This repository has been archived by the owner on Apr 3, 2020. It is now read-only.

Improve error message when S3 bucket name is taken #32

Open
crea1 opened this issue Jan 23, 2018 · 3 comments
Open

Improve error message when S3 bucket name is taken #32

crea1 opened this issue Jan 23, 2018 · 3 comments

Comments

@crea1
Copy link

crea1 commented Jan 23, 2018

Was struggling for a while with running concourse-up deploy <projectname>. And got stuck with this error message.

Forbidden: Forbidden
	status code: 403, request id: 1234567890123456

After alot of headscratching we found out this was because the S3 bucket name was already taken. It looks like the bucket name is constructed like this.

concourse-up-<projectname>-<region>-blobstore
concourse-up-<projectname>-<region>-config

Probably a lot of people will try to use "ci" or something similar as project name and get the same error as I did. A better error message would've saved me some time on debugging.

Cheers,
Marius

@karlkfi
Copy link

karlkfi commented Apr 9, 2018

Duplicate of #17 but thanks for the extra details.

@will-gant
Copy link
Contributor

Hi. I agree that kind of error is completely unhelpful, and that it'd be better if we presented something a bit more informative when there are AWS errors.

I've added a story to our Icebox, which will be considered by the PM in due course.

@vanjan
Copy link

vanjan commented Aug 20, 2018

I'm also getting a 403 but must be a different reason, as I don't have any s3 buckets yet. How can I debug this further?

Forbidden: Forbidden
	status code: 403, request id: 0716BC31FDCF4F05, host id: ciP7058tk3s8XYKGSor69G8Olv8W8XGUGGkqeTB+dX4Io0TCRnxrT5ROtIxkefMGobp876n6mJI=

edit: oh, s3 bucket names have to be unique across all AWS users...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants