- Newest
- Most votes
- Most comments
Thanks for looking into this. I have checked and the ACLs have a 100 rule allowing all comms, so I am assuming there's no issue there. The endpoint is within vpc1 in account1 and the s3 service is provisioned under account2. S3 in account2 is not within a VPC so I did not check if there is VPC peering.
Also, there is no specific route configured. My understanding is that a VPC interface endpoint will have an IP address within the CIDR range of the subnet and hence doesn't need a route? Please advise if I am mistaken.
It is an interface endpoint that I have configured with the intent to have it used by an on-premise application. I am testing the endpoint at the moment through AWS Cloudshell from account1. I also have a Lambda function configured in account1 and I am facing the same issue with the lambda function as well.
When I do a nslookup to the vpc interface endpoint, it resolves to the correct IP addresses. When I do t a telnet on 443, however, it just times out. Thanks
Hi, I'm facing a similar issue. Did you ever resolve yours?
I assume you have VPC peering configured along with correct routes in each route table associated with said subnets? No ACLs in place to prevent communication? Where are you running the CLi from also?
If you have it in another VPC then you will need peering or transit gateway setting up. You’ll also need routes to the other CIDR range.
If there’s no connection between VPCs you’ll never be able to connect to the endpoint.
Lambda by design has access to the internet and s3 without setting up any endpoints. This changes if your lambda is attached to a vpc.
You are correct that an Interface Endpoint gets an IP (ENI) from your subnet.
Did you create a security group (or edit an existing one) to allow the resources in your VPC to communicate with the endpoint network interfaces for the VPC endpoint?
If your resources are in a subnet with a network ACL, verify that the network ACL allows traffic between the endpoint network interfaces and the resources in the VPC.
Did this help you resolve the issue?
Relevant content
- Accepted Answerasked a year ago
- asked 2 years ago
AWS OFFICIALUpdated 6 months ago- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
Turns out that this is a DNS issue. I do not have DNS Hostnames enabled on my VPC and the endpoint. I have private DNS configured through a DHCP option set. It looks like my private DNS is unable to resolve AWS provided regional endpoint FQDN. It also doesn't route the request to the internet for resolution. I will need to find a fix to route this request to the VPC's DNS so the endpoint FQDN can be resolved.