-
Notifications
You must be signed in to change notification settings - Fork 233
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
Error getting DynamoDb local latest tar.gz location undefined: 403 #294
Comments
I'm getting the same error, apparently AWS changed the domain to Edit: |
@matAlmeida Thanks, we will wait for the new release then. |
In the meantime, manually editing the |
@benjiJanssens it worked !! thanks a lot ! |
@AshanFernando hey there! now that 99x/dynamodb-localhost#78 is merged, could we get a release to NPM which includes the fix? |
@cnuss you're in the wrong repo 😄 as soon as |
it appears |
They should really make this configurable. |
any update on this issue? it's blocking our CI. |
youre not alone :') |
Sad nothing happens :( |
It worked for me! Thanks! |
I've found a less-hacky way of getting the URL to update, and considering you're using NPM 8.3.0+ (also worked with NOTE: I needed to clear my
Ref: 99x/dynamodb-localhost#78 |
Any ETA on when this is going to get published? |
To whom it may concern: I faced this issue last week and CircleCI was really not liking it. I ended up adding the following in the "scripts": {
"postinstall": "sed -i 's|http://s3-us-west-2|https://s3-us-west-2|g' ./node_modules/dynamodb-localhost/dynamodb/config.json && sed -i 's|require(\"http\")|require(\"https\")|g' ./node_modules/dynamodb-localhost/dynamodb/installer.js",
...
},
Is it a bit hacky? yes, but I can get over it for now. I'm using |
@jespinal you could use patch-package for that Edit: adding the link |
I missed a line in my original comment, it also needs to be set in
Also found some issues with ourdering so make sure |
I have a doubt, why using pnpm the folder |
I fixed it by simply copying over the |
Doesn't work for me either |
Do we have fix this as of now ? |
man, this long and no fix? this is annoying |
Last publish of the library was 2 years. Should we consider it as dead ? |
@ehtesham1996 Seems like it. I guess a fork would be a viable option |
In the meantime, manually editing the thank you so much: |
This issue appears to have been fixed in the latest release without need for any manual editing or switching the config json values |
The newest version via npm is serverless-dynamodb-local 0.2.40 and uses dynamodb-localhost 0.0.9 still with the old url. As matAlmeida commented on Mar 8: PR 99x/dynamodb-localhost#78 merged but is not released yet. In the comments are some suggestions provided on how to fix the issue:
I used the command from jespinal:
|
FYI: This package ( Solution: You can use serverless-dynamodb, a maintained fork, instead. (Disclaimer: I am a contributor to this fork). It is a drop-in replacement for this package, and is updated to fix this bug. This is a drop-in replacement for
Of course, it's all still open-source and MIT licensed. Ownership of this new package sits with a registered charity, that is committed to maintaining the package into the future and is open to contributions from the community. In any case would be open to feedback on the fork - can drop create an issue in that repository or email me (address on profile). |
Thank youu! |
Hi, I am getting Error: "Error getting DynamoDb local latest tar.gz location: 403" after doing installing serverless-dynamodb-local.
Here is the full description of the error message:
Started downloading dynamodb-local from http://s3-us-west-2.amazonaws.com/dynamodb-local/dynamodb_local_latest.tar.gz into ***/.dynamodb. Process may take few minutes.
✖ Uncaught exception
Environment: darwin, node 16.17.0, framework 3.26.0 (local) 3.25.1v (global), plugin 6.2.2, SDK 4.3.2
Docs: docs.serverless.com
Support: forum.serverless.com
Bugs: github.com/serverless/serverless/issues
Error:
Error: Error getting DynamoDb local latest tar.gz location undefined: 403
at ClientRequest.
at Object.onceWrapper (node:events:628:26)
at ClientRequest.emit (node:events:513:28)
at ClientRequest.emit (node:domain:489:12)
at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:674:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
at Socket.socketOnData (node:_http_client:521:22)
at Socket.emit (node:events:513:28)
at Socket.emit (node:domain:489:12)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
at Socket.Readable.push (node:internal/streams/readable:228:10)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
It seems that the bucket doesn't authorize my request!
The text was updated successfully, but these errors were encountered: