You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2020. It is now read-only.
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.
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
The text was updated successfully, but these errors were encountered:
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.
Was struggling for a while with running
concourse-up deploy <projectname>
. And got stuck with this error message.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.
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
The text was updated successfully, but these errors were encountered: