-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The specified bucket is not valid. #98
Comments
And same for applying a custom domain name:
|
It seems to be the way the bucket is referenced in the codebox-tools. See these lines: codebox-npm/.serverless_plugins/codebox-tools/index.js Lines 12 to 16 in 8690e34
They are returning ${self:provider.environment.bucket} which is what is actually specified in the serverless.yml.
It seems serverless only has these values populated inside the handlers, so each handler should look it up itself, instead of doing it in the constructor. Like so: migrate() {
this.bucket = this.serverless.service.resources
.Resources
.PackageStorage
.Properties
.BucketName; Making this change in the migrate function has it working, but I'm now getting Access Denied errors, which are probably on my end. |
Access Denied seems to be related to missing Encryption on the S3-Put |
I was having exactly the same issue with host migration....
A bit of an ugly workaround (OK a very ugly workaround) but... temporarily hard-coding the bucket into serverless.yaml worked for me...
|
Any update on this? I set up a custom domain in API gateway, but when I run
Hard-coding the bucket the
|
@thomastoye to fix this issue just add
|
Its seems I cannot run
serverless remove --stage prod
. I am sure the correct bucket has been exported:The text was updated successfully, but these errors were encountered: