Can not access S3 via VPC endpoint in Lambda

If you want to allow an AWS Lambda to access Amazon S3, use one of these methods:

• Do not associate the function to a VPC. Access is then automatic.
• If the function is attached to a public subnet in the VPC, associate an Elastic IP to the Lambda function's ENI that appears in the VPC (Not recommended)
• If the function is attached to a private subnet in the VPC, launch a NAT Gateway in the public subnet and update Route Tables. Traffic will flow to the Internet via the NAT Gateway.
• Add an Amazon S3 VPC Endpoint in the VPC and update Route Tables. Traffic will flow through that instead of the Internet Gateway.