Even if you place a Lambda function in a public subnet of a VPC, you cannot directly interact with the Lambda function using the public IP address (assigned to Lambda's ENI). The ENI and its associated IP addresses are only used for outbound connections from the Lambda function.
In case you need to expose Lambda to the public internet, you can use API Gateway + Lambda or ALB + Lambda. Which one is better depends on your specific use case and requirements. You can use ECS + ALB as well, I wouldn't say it's more "public internet" friendly approach, difference in the approaches related more to difference between ECS and Lambda.
What do you think about Lambda + VPC Integration. When there is a requirement for having a Public IP Address?
I know it is possible, but I think there are more "public internet" friendly solutions. Like ECS through a Load Balancer for example..
It's quite an interesting question.
Even if you place a Lambda function in a public subnet of a VPC, you cannot directly interact with the Lambda function using the public IP address (assigned to Lambda's ENI). The ENI and its associated IP addresses are only used for outbound connections from the Lambda function.
In case you need to expose Lambda to the public internet, you can use API Gateway + Lambda or ALB + Lambda. Which one is better depends on your specific use case and requirements. You can use ECS + ALB as well, I wouldn't say it's more "public internet" friendly approach, difference in the approaches related more to difference between ECS and Lambda.