Lambda to VPC connection invisible

Question

Hello,

The info from Management Console states:

> All Lambda functions run securely inside a default system-managed virtual private cloud (VPC). However, you can also configure your Lambda function to access resources in a custom VPC.

After I connect a Lambda to a custom VPC from Management Console -> Lambda Screen -> Configuration -> VPC, I do not see any Endpoint for Lambdas in the endpoints list of the VPC, even if the connection works. How does Lambda connect to the custom VPC ?

Thank you,  
Mihai ADAM

Accepted Answer

Hello.

> After I connect a Lambda to a custom VPC from Management Console -> Lambda Screen -> Configuration -> VPC

I think your settings are correct.  
Connecting Lambda to a VPC does not create a VPC endpoint.  
If you have configured it correctly, check the ENI from the EC2 console and the Lambda Hyperplane ENI should have been created.  
https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html#vpc-configuring

An interface type of "lambda" will be created as shown below.  
![a](/media/postImages/original/IMZLoh4lKjR2aD5BFCBGEXIA)

Access resources within the VPC via this created ENI.  
https://docs.aws.amazon.com/lambda/latest/dg/foundation-networking.html#foundation-nw-connecting  
> Lambda accesses resources in your VPC using a Hyperplane ENI. Hyperplane ENIs provide NAT capabilities from the Lambda VPC to your account VPC using VPC-to-VPC NAT (V2N). V2N provides connectivity from the Lambda VPC to your account VPC, but not in the other direction.

Lambda to VPC connection invisible

Contenus pertinents