Hi Everyone, I'm having trouble with the local dev environment. I have a Lambda in a VPC with a Security Group that allows all egress, triggered by an S3 event. It works fine when fully deployed. When using the local dev environment, it simply hangs and times out (even for much longer time limits):

2022-03-25T16:19:13.067-04:00	START RequestId: 31bcc1ae-8648-4f40-84c5-a2574533fe58 Version: $LATEST 
2022-03-25T16:19:13.156-04:00	2022-03-25T20:19:13.097Z 31bcc1ae-8648-4f40-84c5-a2574533fe58 INFO connectAndSendMessage()
2022-03-25T16:19:18.076-04:00	END RequestId: 31bcc1ae-8648-4f40-84c5-a2574533fe58
2022-03-25T16:19:18.076-04:00	REPORT RequestId: 31bcc1ae-8648-4f40-84c5-a2574533fe58 Duration: 5007.89 ms Billed Duration: 5000 ms Memory Size: 128 MB Max Memory Used: 80 MB Init Duration: 469.73

Any ideas for what to troubleshoot?

is it possible to test it while conditionally disabling vpc in local dev

@Mendel Lerner are your other functions also in the same VPC? And do they also time out?

Is your local dev environment running in the same VPC via a VPN client?

Functions outside the VPC work fine. The Lambda seems to work from the AWS side (which is where the logs above are from) but the websocket never connects to my machine, I get the timeout log and whatever runs in the stub setup, but nothing in the

_<http://ref.ws|ref.ws>.onopen

function

@Mendel Lerner just checking, are you still having this issue?

@Jay, Thanks for checking in. I stopped work on the project for a few days and when I came back it was working fine again

Oh interesting. Feel free to post again if something comes up!