Menu
I cant save my Lambda (Node.js)function on AWS with VPC selection, its not saving at all and did not get any message from AWS.
When I try to save without VPC selection its working but then I select VPC its not saving at all.
Its always showing same status save.
When I click on this, its not saving after refresh its again back to the previous form.
967
This is not possible with Lambda. Lambda functions can provide access only to one single VPC. If there are multiple subnets and are specified, then they must all be in the same VPC. You then can connect to the other VPCs by peering your VPCs.
Lambda functions always run inside VPCs owned by the Lambda service. As with customer-owned VPCs, this allows the service to apply network access and security rules to everything within the VPC.
To save a file, with the file open and its contents visible in the editor pane, choose File, Save on the menu bar. To rename a file or folder, right-click the file or folder in the Environment window.
This happens most of the time when the role you have configured for lambda does not have access to the VPC. There is an error appearing at the top of the screen under the Designer tab, but it is difficult to catch and not always visible.
To resolve this, modify the role you have configured in lambda to include the policy named "AWSLambdaVPCAccessExecutionRole". Then you will be able to save this function.
https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html
180
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
