Check below things.
a--Fabric client (EC2 instance is in same VPC used in creating VPC Service endpoint).
b--Fabric client (EC2 instance is using same Security Group used in creating VPC Service endpoint).
c--Port 30001 to 30004 are allowed in inbound rules in the security group.
2ndly there is a mistake in AWS documentation, the 2nd url should be used with telnet, instead of Curl. it should be:
telnet CAEndpointURL 30002
I have already pointed out this mistake to AWS Support and they confirmed that they will update the documentation.
One thing more is that the port is not guaranteed to be 30002, but the exact value will be returned in the get-member API.
Edited by: Ikram on Feb 3, 2019 5:59 PM
Thanks, it was the security group TCP port not being open that was the issue. In retrospect, it seems clear, but a combination of my own lack of network experience and the documentation not mentioning it meant I missed it. Thank you for the help. I suggest that this be added this to the prerequisites section of the documentation too.
- asked 7 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 5 months ago
- How do I delete my Network Load Balancer that's associated with VPC endpoint services (PrivateLink)?AWS OFFICIALUpdated a year ago
- EXPERTpublished a month ago