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 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.
I try it but invalid Destination
Please suggest me Another solution.
How do I configure VPC route tables for Traffic Mirroring?Accepted Answerasked 2 years ago
VPC subnet routing.Accepted Answerasked 6 months ago
Route tables for Using Amazon Managed Prometheus with interface VPC endpointsasked 23 days ago
Accessing S3 Gateway VPC Endpoint from another VPC (VPC Peering established between both source and destination VPCs)Accepted Answerasked 2 years ago
Benefits to S3 cross-region access with VPC peered interface endpoints vs. public internet using NAT gateways?Accepted Answerasked 5 months ago
How to setup interface VPC endpoints in a multi tier architecture?Accepted Answerasked 2 years ago
Access to Public S3 within private subnet in VPC without Internetasked 3 years ago
Accessing RDS in Private Isolated VPC using IAM Authenticationasked 7 months ago
Ingress rules for a private subnet NACL with VPC endpoints: Are AWS service CIDR ranges required?Accepted Answerasked 7 months ago
Lambda in VPC can't access S3asked 5 months ago