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.