Lambda with vpc and internet access

Hi,

you can create a NAT Instance and use it instead of a NAT Gateway. If an instance type under the free tier has sufficient performance for your use-case. When using a NAT instance you have to take care of managing the instance and you will also loose redundancy that is built into the NAT Gateway.

Cheers,
Philipp

If your Lambda uses public subnets you can't grant it a public IP address to be able to use the IGW, but it is possible to attach an EIP to the Lambda's ENI. Since the VPC Lambda networking improvements of 2019/20 these ENIs are long-lived but they still may be reclaimed if unused for consecutive weeks. Also if you have high concurrency of Function execution additional ENIs may be automatically created which of course won't have EIPs. If you can manage these issues, e.g. ensuring the Function is invoked occasionally and that concurrency is limited, this may work for you, and may be preferable to managing your own NAT Instance. Of course NAT GW is still the AWS-approved solution.