johnc44

Just experienced the same issue. Seems to happen when redeploying the same lambda, so we have to tear it down and recreate it. I will try the solutions given, but...

> The workaround I have found is to do : > > ``` > Events: > Proxy: > Type: Api > Properties: > Path: /{proxy+} > Method: any > ```...

The way I see this problem is that it is an accumulation over time. So if I deploy my lambda today, then keep making changes, eventually it will hit a...

@tianmarin - did this stay working for you? I've not done anything with it yet, but we've not seen the problem for a little while. (Probably because we've not done...

This problem hasn't occurred for years, but recently we added some new APIs and it cropped up again. We do have a single lambda that services quite a lot of...

Thanks very much for the reply. I could have sworn I read that one or the other was required, but I've just tried it and it does seem to work....

Thanks very much for the reply. I think being able to define responses might well help. I had a very quick look at the PR and it seems like you...

Thanks, @TheSriram for the reply. Sorry it took me so long to respond, but I needed to find time to play about with your suggestion. Am I right in thinking...

Digging around in the error some more, it does look like this is a pip problem. `pip download -r requirements.txt --dest temp` - this throws the same error as I...

> Something I'm noticing here: > > ``` > "'https://${FrontEndDomainName}.${dnszone}'" > ``` > > The inside of the string would thus be: > > ``` > 'https://${FrontEndDomainName}.${dnszone}' > ``` >...