Lambda function VPC in us-east-1 doesnt work after changes in us-west-2

Question

Hello,
Earlier I was tasked to remove a whole project that we had located in us-west-2 region. I removed several EC2 instances, elastic IPs, volumes, etc...
When I was testing my lambdas in us-east-1 I noticed the connection to my Mongo DB was failing. After doing some tests, I noticed that if I have the VPC active in my lambdas it wouldn't work but as soon as I removed it, the petition went through. 
It doesn't make sense to me why this happens as I only removed resources from my us-west-2 region. 
I've more than tripled checked that the VPC and everything is correct and I just can't find what is happening.

MarioAcr94 · Accepted Answer

Hi,

Thank you for your promptly response, I'm honestly impressed. 
I checked the subnets again and I honestly don't know how or why but all of them changed from a private subnet(the one previously configured and working) to a public one (the one that didn't work) 
I changed them back and it worked fine.

Thank you very much.

Riku_Kobayashi · Answer

Hello.

Could you please share the route table settings of the subnet to which you connected Lambda?  
Were you able to connect to MongoDB even if Lambda was originally connected to the us-east-1 VPC?  
For example, you may be accessing Mongo DB from a VPC in us-east-1 via a VPC in us-west-2 using something like TransitGateway.

Leo K · Answer

How is the removal of resources from us-west-2 related to the Lambda functions in us-east-1 being attached to a VPC? Were the functions in us-east-1 previously *not* in a VPC and you attached them to a VPC (in us-east-1) for the first time at the same time that you removed resources from us-west-2?

Lambda function VPC in us-east-1 doesnt work after changes in us-west-2

Add your answer

Relevant content