I have been able to run my s3 commands just fine. But today when I try from my local PC (OSX, command-line cli calls) as I always have when testing, I get:
aws s3api create-bucket --bucket our-bucket-name --region us-west-2 --create-bucket-configuration LocationConstraint=us-west-22
and it is bombing today out of the blue with A client error (SignatureDoesNotMatch) occurred when calling the CreateBucket operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.
what could cause this all of a sudden? I rebuilt a previous Travis build using some AWS credentials I had addd as enviornment variables in Travis and that build still works with the asw credentials I specified, but I've not had to specify my AWS credentials locally for aws cli calls or if I did, then I don't remember but regardless this was working fine yesterday.
Here's another call that was working just fine up till now
aws s3api head-bucket --bucket mayfield-gizmo-react-web-admin-wa-19
A client error (403) occurred when calling the HeadBucket operation: Forbidden
So why was I able to make calls fine without specifying credentials locally, but now it's complaining all of a sudden?
So why was I able to make calls fine without specifying credentials locally, but now it's complaining all of a sudden?
I don't know what it was but I reset my credentials locally and it's working. No idea why the hell it would just stop using the credentials that are already set locally which I guess I did do at some point:

This error occurred when you AWS credential set using environment variables And the key has special characters in my case "/"
Related issue:
https://github.com/aws/aws-cli/issues/602
^-- This solved my problem
Thank you, worked like a charm!
Most helpful comment
I don't know what it was but I reset my credentials locally and it's working. No idea why the hell it would just stop using the credentials that are already set locally which I guess I did do at some point: