https://serverless-stack.com/ logo
Join Slack
Powered by
I’m running into an issue, which I believe used to...
# help
g
I’m running into an issue, which I believe used to work in the past, but is now broken .. maybe? When deploying a sst.Api into a VPC and private subnets, it works fine in 
deploy
but fails in debugging 
start
mode. I noticed that the debug lambda functions are not deployed into the VPC. Could that be the issue?
t
What kind of subnet is it
g
private with NAT
t
Hm that should work, I'll be home in a bit and send you some debugging steps
g
tx
that’s what I’m saying, it used to work on different projects and now, not! ttyl
FWIW, the request never makes it to my local machine
The cloudwatch log for the primary Lambda shows:
and then it times out.
t
Whew got caught in a downpour 🌧️
ok let me take a look
So when you say the sst.Api is in a VPC, do you mean the lambda functions are in the vpc?
Not sure if this is a viable work around for you but in the past I disabled vpc for local development with 
vpc: !scope.local && vpc
g
Indeed. I just realized that my NAT may be in a private subnet. Let me see if that resolves it.
t
When we've seen this before it's generally been because the lambda couldn't talk to the internet
a
I HAVE THE SAME ISSUE!!!
I thought it was just me.
I mean, sometimes works, and sometimes not.
To solve it I have to delete my stacks.
And start oven.
This happens when I do this… 1. start 2. deploy 3. start Then it doesn’t receive any more messages.
Im getting crazy for this problem 😞
g
It was the NAT. I accidentally put it in the private subnet. argh! thanks @thdxr
a
@Guy Shechter did you setup nat in your stack?
g
no @Adrián Mouly
a
Ah ok.
g
let me know if you need any help
a
Yeah going to try something else, it doesn’t fail all the time, only when doing start.. then deploy.. then start again.
I mean, in different steps, not all together.
Open in Slack
PreviousNext
Powered by