1 Answer
- Newest
- Most votes
- Most comments
1
The endpoint URL is usually setup and accessed from a 3rd party AWS account and not the same account your NLB exists. Ensure your security group allows access to the service on the correct Port.
Can you confirm how and where have you created the EndPoint (Not the End Point Service)? https://docs.aws.amazon.com/vpc/latest/privatelink/create-endpoint-service.html#create-endpoint-service-nlb
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- How do I delete my Network Load Balancer that's associated with VPC endpoint services (PrivateLink)?AWS OFFICIALUpdated 2 years ago
I allowed all traffic in the security group. Endpoint is created in different account. Because our customers are reporting issues that they are unable to access the app, I replicated the endpoint setup in my account and tested it. I am confused that I can access app through NLB but not through endpoint. I rechecked if there are any traffic blocks and I am pretty sure that I didnt block any traffic at any level.
I don’t suppose you could share screen shots of endpoint service and endpoint with sensitive info removed?