- Newest
- Most votes
- Most comments
Interface endpoints for AWS services do not show up as a destination in a route table. Instead, they appear as network interfaces in your VPC. In this case, your VPC has a 10.194.0.0/16 address; the endpoints will have IP addresses in that range.
To use the endpoints you must use the appropriate DNS name for the endpoint. This is mentioned in the documentation page you link to above: You need to set up your application to use that name which will be com.amazonaws.region.aps-workspaces
or com.amazonaws.region.aps
depending on what you're trying to do. The DNS names will resolve to the 10.194.x.x address in your VPC and from there it will work as expected.
Hi @Brettski@AWS,
I try it but invalid Destination
Please suggest me Another solution.
No, you cannot route to an Interface Endpoint. In your application, put the private DNS name of the endpoint as it is displayed in the console (where you created the endpoint). For example, if you're using Python and boto3 you must specify the
endpoint_url
as per the documentation.
Relevant content
- Accepted Answerasked 5 years ago
- Accepted Answerasked 3 years ago
- asked a year ago
- Accepted Answerasked 19 days ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 6 months ago
- How do I use an interface VPC endpoint to access an API Gateway private REST API in another account?AWS OFFICIALUpdated 6 months ago
invalid Destination. Please see picture below my answer.