The VPC endpoint has an associated security group. The ENI for Lambda Function's VPC attachment also has a security group associated. Please ensure that the VPC endpoint's security group has an ingress rule allowing traffic from the Lambda Function's security group.
Please see here for more details on accessing services using a VPC endpoint.
inbound rule of security group for EC2 Instance in private subnetasked 10 months ago
Bastion Host (Public Subnet) unable to reach RDS (Private Subnet) in my VPCasked 2 years ago
Routing network traffic between two EC2 instances in the same subnet to a firewall appliance in another VPCAccepted Answerasked 8 months ago
Is the sessionId in PutEvent related to the session in the HRNN model?asked a year ago
If a Lambda @ Edge function calls DynamoDB, does the traffic stay within the AWS network?Accepted Answerasked 2 years ago
Implement Security on the Web Application Without Touching the Web Applicationasked 9 months ago
Lambda (private subnet) <- ingress request< - gatewayAccepted Answerasked 8 months ago
Anything on the roadmap for this limitation "You cannot reference the security group of a peer VPC that's in a different Region. Instead, use the CIDR block of the peer VPC."asked 4 months ago
Lambda in private subnet cannot reach DynamoDBasked 2 months ago
Best way to filter to find a Lambda function's Network interface IP address via Boto3?asked a month ago