Hi. I've connected my an ApiGateway REST resource to a lambda function. It works correctly when I use only the lambda function name (not the alias or the version) in the "Lambda Function" field of my REST resource's "Integration Request" page. However, when I add an alias to my lambda function, and set the "Lambda Function" to use the ":alias" at the end of the lambda function, and then set the correct permissions on my lambda alias, the requests do not make it through.
I have CloudWatch logs from my ApiGateway from one of these requests. Here is the relevant bit:
(57980943-e0ee-4556-a70d-477ea10f0b43) Sending request to https://lambda.us-west-2.amazonaws.com/2015-03-31/functions/arn:aws:lambda:us-west-2:**************:function:interact/invocations
(57980943-e0ee-4556-a70d-477ea10f0b43) Execution failed due to configuration error: Invalid permissions on Lambda function
You can see that ApiGateway is attempting to post to the unaliased function name, instead of the aliased one. I only have LambdaInvoke permissions on the aliased function, not the unaliased one, so the error message makes sense. What doesn't make sense is why ApiGateway is not using the alias that I specify in the "Integration Request" page of my resource.
Can anyone shed some light on this please?
It would be helpful to see the actual
urithat is returned for the integration, using get-integration@Farski
And here's a CloudWatch entry for the ApiGateway api:
You can see that the alias is not included in the request.