nprapps / nprapps/dailygraphics-next
`SignatureDoesNotMatch` error when deploying to AWS
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 72
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
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 theirAWS_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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing deployment from a fresh dgnext install on macOS using zsh and an AWS_SECRET_ACCESS_KEY containing '/'. Compare the failing case with a key without '/', and consult the linked aws-sdk-js thread for relevant behavior. Done means establishing whether the key character causes the error and documenting or fixing the deployment behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100