You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 15, 2026. It is now read-only.
Lambda Deploy command sets Lambda function's network to "No VPC" #78
Looking at this code, you should enter the VPC settings in your config file. From your question it isn't clear wether you did, but make sure you have entered the subnet_ids and security_group_ids correctly
I just created a pull request to address this issue. In my PR I added a --preserve-vpc command line flag that allows you to not worry about setting the VPC info in the config.yaml
I'm not sure if this is a bug in the library, or how I've setup AWS / Lambda.
But everytime I run "lambda deploy" the lambda function I'm deploying to is set to "No VPC", dropping the subnets and security group.
Any ideas why this might be happening?