For a Kinesis stream, I created a proxy API using AWS API Gateway. I added a custom authorizer using python Lambda for the proxy. After publishing of lambda function and deploy of API, I was able to successfully test the API using Gateway Test functionality. I could see the logs in cloud watch which had detailed prints from custom auth lambda function. After successful authentication, API Gateway pushed the record to my Kinesis stream
However, when I call the same API from Chrome Postman client, I get 500 Internal Server Error and response headers includes X-Cache → Error from CloudFront, x-amzn-ErrorType → AuthorizerConfigurationException
Lambda auth function returns the policy which allows executing a request for my API. Policy Document returned is:
Why does the request fail from Chrome or curl but the same API test works fine from API Gateway?