I found the answer myself.
od -c token.sign.b64
to view the actual byte contents of the file showed that it had \n chars in it which would have been generating the error.
So instead of just running base64 on the file I ran this to ensure that no \n got into the output file:
base64 token.sign | tr -d \n > token.sign.b64
AWS IoT Custom Authorizer Not working for HTTP GET GetRetainedMessageasked 7 months ago
IoT Events custom payload errorAccepted AnswerMODERATORasked 2 years ago
How can I restrict certain topics when not using AWS Cognito?asked 2 years ago
How do I see the posts I am following?asked 6 months ago
Error when running test-invoke-authorizer: tokenSignatureasked 4 years ago
Can I use API Gateway cache invalidation with a custom authorizer ?asked 8 months ago
IoT Events convert number to string for SNS custom payloadAccepted Answerasked 9 days ago
I am not able to find this solution in sagemaker jumpstartasked 8 months ago
Why am I not able to create alerts and set alert thresholds?asked 2 months ago
I am unable to delete my AWS Amplify projectasked 4 months ago