AWS introduced Hyperplane Networking for Lambda in 2019, which invalidates some of the claims in this article, like :
Elongated cold starts with Lambda fns in VPC.
Exhausting ENI Limits for the IP address which are associated to a subnet.
Creation of ENIs and concurrency is managed much better by AWS. Hyperplane now creates a shared network interface when your Lambda function is first created or when its VPC settings are updated, improving function setup performance and scalability. This reduces the Cold Start time considerably. In many cases, the cold start time has gone down one or two orders of magnitude in milliseconds.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
AWS introduced Hyperplane Networking for Lambda in 2019, which invalidates some of the claims in this article, like :
Creation of ENIs and concurrency is managed much better by AWS. Hyperplane now creates a shared network interface when your Lambda function is first created or when its VPC settings are updated, improving function setup performance and scalability. This reduces the Cold Start time considerably. In many cases, the cold start time has gone down one or two orders of magnitude in milliseconds.