1 Answer
- Newest
- Most votes
- Most comments
0
If you are using private link then transit gateway is not needed. Connectivity between VPC is certainly not required as PrivateLink provides private connectivity between virtual private clouds (VPCs)
Some things to check..
- In your public VPC, your NLB is internet facing
- In your public VPC, your NLB is on a public subnet
- Your NACL's in the subnets allow bi-directional traffic
- Your Security groups on the endpoints need to allow traffic from the NLB IP addresses in the Public VPC
answered 13 days ago
Relevant content
- asked 2 months ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
Thanks for the reply Gary.. For NACL part i have allowed all for both inbound and outbound For 4th point i have allowed all the traffic in endpoint security group
Rest point i have already followed..
During your testing, what parts work? i.e. connecting to the endpoint service in the public VPC. Connecting to the NLB within the Public VPC.. See if we cant try and narrow the issue down
When I am hitting endpoint service dns from my public instance which is in public vpc, i am able to get the reply. But when I am trying to create target group for public NLB i have used ip of interface endpoint, it is showing me unhealthy though I have accepted the connection in endpoint service. Also sg of interface endpoint allowing all the traffic It seems like only my target group of public NLB not able to connect with interface endpoint dns