SignatureDoesNotMatch error when deploying to AWS

[alykat]

Have seen two people (one on the team, one external) report a SignatureDoesNotMatch error from aws-sdk-js when deploying to AWS. (One person reported this was an issue for deploying new graphics, but not for rewriting existing graphics.)

Common to both:

• Fresh dgnext installs
• On Macs
• Using zsh rather than bash
• A / character in their AWS_SECRET_ACCESS_KEY (some comments in this thread suggest that this can be an issue)

For both, refreshing their keys to ones that didn't have a / ended up fixing the issue.

I can't say definitively that having a / in the key is a problem for all users: Another member of the team has the same setup and has not had an issue deploying. But if this comes up again, refreshing keys is certainly a thing to try.

/cc @thomaswilburn in case it's of interest.

[thomaswilburn]

I just pushed a commit to our rig that moves to the latest version of the SDK, and encountered this error when I was using the ListObjects command. It went away when I moved to ListObjectsV2, which is compatible with the arguments we're currently using. Given that this is happening for your users when calling PutObject during deployment, I don't know that it'll fix things for sure, but it might be worth a shot to try a branch with our changes and see if they fix anything in the future (and probably a good idea to upgrade the SDK anyway, honestly).