-
Hello Mogomotsi,
Thank you for your insightful feedback regarding the question. After reviewing the details, it does appear that the scenario and options rely on outdated behavior related to Lambda functions in VPCs.
As per the latest AWS documentation, the Elastic Network Interface (ENI) associated with a Lambda function is created when the function itself is created rather than during each invocation. This means that errors related to subnet ENI or IP exhaustion during invocation are no longer valid concerns.
Once an ENI is created, it is reused for all subsequent invocations of the Lambda function, which means that issues related to IP address exhaustion at the time of invocation would not occur unless the function configuration changes significantly. Additionally, if the number of connections exceeds this limit, Lambda automatically scales the number of ENIs based on network traffic and concurrency requirements.
We will update the item to reflect the current Lambda VPC functionality. Thank you again for helping us improve the accuracy of our content. If you have any further suggestions or questions, please feel free to share them!
Regards,
Nikee @ Tutorials Dojo
