All Questions

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

How to know if my Lambda Authorizer for API Gateway is caching results?

I have a Lambda Authorizer for an API Gateway API with one resource and three methods - PUT / GET / DELETE. Each method uses the same Lambda Authorizer, the TOKEN kind, to verify a JWT from Cognito. An IAM policy is returned by the Lambda which allows PUT / GET / DELETE actions on the resource. The authorization and policy work fine -- I just don't know if the result is being cached by API Gateway. When I look at the API Gateway execution logs, every request seems to be calling the Lambda Authorizer. Every API Gateway execution log has a line like this: ``` Sending request to https://lambda.us-east-1.amazonaws.com/2015-03-31/functions/arn:aws:lambda:us-east-1:123456789012:function:MY_LAMBDA_FUNCTION:prod/invocations ``` **Does this invocation of the Lambda function mean that the Lambda Authorizer is not caching properly?** After the "Sending request" log line, there's a line like "Authorizer result body before parsing" and then this line: ``` Using valid authorizer policy for principal: *****user ``` **Does this statement indicate that the Lambda Authorizer using a cached policy?** The strange thing is...when I check the Lambda logs, the execution times vary wildly, almost as if the Lambda itself is caching the result...but I think the caching happens on the API Gateway side? What's going on here? Sample of Lambda duration times: 529ms, 10ms, 217ms, 213ms, 8ms, 2ms
0
answers
0
votes
20
views
profile picture
asked a day ago

Why AWS is not allowing us to receive client inquiries on our website through emails?

We have recently migrated to AWS from the previous hosting provider. However, since then we have stooped receiving client inquiries put on our website, in the form of emails which we used to get seamlessly earlier. We tried to contact them but were asked to pay for any technical support, so we did. We requested them to enable port 25 and they asked few questions like use-case for sending mail from EC2 and spam prevention mechanisms. After successfully answering both the questions, they said "We have lifted the restriction for your account in the following > region(s): ap-south-1" - we didn't understand what it is. So check if the email function is working. But it wasn't. Therefore, we wore back to them saying that it is still not working. To our surprise, they sent us this "After a thorough review, we confirmed our original finding and cannot grant your request. Please consider looking into the Simple Email Service (SES). We cannot assist you further with this issue and we may not respond to additional messages on this subject" Since then, they are not responding. We are still wondering how can they deny helping us sort out the issue or at least explain properly why certain things are not feasible at their end. It is totally unacceptable to bound customers to keep purchasing additional services by sending such rude emails and poor customer support. Inquiry [xxxxxxx] *Edit: Removed AWS Account ID - Ben G.
1
answers
0
votes
20
views
asked 2 days ago