Anybody else experienced this issue in Lambda? My lambda is timing out, but checking in the logs, there is nothing there… only couple of warnings, but looks like is taking long time to do the cold-start and it doesn’t log anything.

When I've seen this kind of thing before it's been because of a problem connecting to some AWS service like SSM or S3 - usually due to VPC config. If you add a log statement to the very start of the handler and at top of the file that's imported that holds the lambda, do you see anything in the logs?

Good call. I’ve been having issues with SSM, apparently reaching the quota limit.

If you run it via SST start, can you add breakpoints in the middy middlewares to see which are getting hit?

Yeah but locally works.

could be, but if it's working locally you'd typically have the opposite problem

Not sure how is that related.

Yeah, that's what I mean. usually the challenge is with getting the local running lambda to connect to services in a vpc but you seem to have the opposite problem, local can connect but deployed can't

Yeah. It’s weird because I think it can connect sometimes.

Have you checked VPC security group? For debugging you can enable all TCP traffic and see if it still timeouts.

I’m going to check it.

I'm guessing this is axios timeout, I would try to enable VPC Flow Logs to gather more data.

Oh didn’t know that existed.

this is also new for me