-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lambda invoke does not accept full ARN as FunctionName #193
Comments
@redinger Thank you for the ticket! According to the page at https://docs.aws.amazon.com/general/latest/gr/sigv4-create-canonical-request.html each path segment in a canonical request should be url-encoded twice (for non-S3 services). However, since we only encode the canonical uri once (code) the signature is off when the full and partial ARNs are used. Changing the code to sign twice was shown to fix the problem but more thought needs to go into if this is the correct general fix. More to come. |
I am also encountering this, is there any update or work around you can recommend? In my case I'm pulling the ARN off of GetResource API call (which would only have ARN). |
Fix merged, release coming shortly .... |
Released in |
Fix Canonical URI encoding during request signing - resolves cognitect-labs/aws-api#193 Port 5ebdfc8c47914f894a240a8290a3715682a1e9bf from aws-api
Dependencies
Description with failing test case
Lambda invoke does not accept a full ARN, or a partial ARN as a FunctionName. According to https://docs.aws.amazon.com/lambda/latest/dg/API_Invoke.html#API_Invoke_RequestSyntax, both of those should be acceptable in addition to just FunctionName.
For comparison, those same invokes work from the command line
The text was updated successfully, but these errors were encountered: