I’m trying to call a configure service node to call an aws endpoint. However AWS’s Signature Version 4 authentication doesn’t appear to be supported yet:
Is there any plans to add this support in.
In my case, I need this auth feature to trigger an AWS Lambda function using a “function url” as my endpoint - Announcing AWS Lambda Function URLs: Built-in HTTPS Endpoints for Single-Function Microservices | AWS News Blog
FYI, curl added support for this authentication type last year, by introducing the new --aws-sigv4 flag. Here’s an example:
curl --verbose --request "POST" --header 'Content-Type: application/json' \
--aws-sigv4 "aws:amz:us-east-1:lambda" \
--user "${PersonalAWSAccessKeyId}:${PersonalAWSSecretKey}" \
--data '
{
"key1": "value1",
"key2": "value2"
}
' \
https://rsuxstsylutbardfsdyqbu0eegxr.lambda-url.us-east-1.on.aws
Docs - Signature Version 4 signing process - AWS General Reference