Skip to content
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

Not using AWS module at all? #5

Open
frankmarineau opened this issue Jun 16, 2014 · 3 comments
Open

Not using AWS module at all? #5

frankmarineau opened this issue Jun 16, 2014 · 3 comments
Assignees

Comments

@frankmarineau
Copy link

Hi there!

I was wondering why you weren't using the AWS module you required in the controller that generates the policy. I see you init it with your config in server.js, but never actually call any of it's S3 methods like getSignedUrl. Is it still doing something behind the scenes? I've been trying to use it since I though it was supposed to abstract some of the policy generating work away, but haven't had any luck with it.

Thanks a lot for this by the way, I finally got through the annoying "SignatureDoesNotMatch" error i kept having before.

@nukulb
Copy link
Owner

nukulb commented Jun 16, 2014

I have been meaning to remove the AWS module completely haven't had a chance to do so.
I will leave this issue open and remove all references to the AWS module.

Thanks for opening the issue.

@nukulb nukulb self-assigned this Jun 16, 2014
@frankmarineau
Copy link
Author

Right, I was starting to wonder if just initializing it was doing something. Thanks again!

@demisx
Copy link

demisx commented Mar 5, 2015

👍 for not using the heavy monster aws-jdk.

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

No branches or pull requests

3 participants