Can we set up VPC config within Jets and have jets deploy set them in the Lambda?
I notice that a jets deploy can take away the VPC settings, and post-deploy I have to manually set these.
Also, if jets deploy supported this, we could spin up a new stack easily.
Same thing for me. Although the security_group_ids and subnet_ids exist on AWS, the deploy fails and can’t understood the reason with the message from CloudFormation. Any ideas @tongueroo?
I had the issue with the autogenerated iamrole used for deploy did not have enough permission.
This is being described here. Not sure if it’s the same issue as this was in Jun 2020. I can confirm it being an issue on jets 2.3.18.
I solved it as follows:
Add the policy named AWSLambdaVPCAccessExecutionRole manually.