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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: