1 Answers
1
In order to use Interface Endpoints you must specify the endpoint name in your code. If you don't specify it then the connection will be made to the default endpoint (for the region you've configured), not the private endpoint you've created.
Relevant questions
SQS VPC interface endpoint and it's usage via AWS SDK v1
asked a month agoAurora Serverless Interface Endpoint preventing VPC delete
asked 2 years agoSQS interface endpoint for cross region access
Accepted Answerasked 2 years agoPushing to SQS through VPC Endpoint from lambda in private VPC fails
asked a year agoHow do I create a VPC Endpoint for S3 Interface?
asked 6 months agoUnable to resolve the private dns name of a Sagemaker runtime VPC interface endpoint
asked a month agoCan not access SQS via VPC SQS endpoint
asked 3 years agoVPC Endpoint Question
asked 4 months agoReading SQS Message via Listener
asked 4 months agoSQS not receiving SNS message
asked 3 years ago
okay, does the endpoint can be deduced from the SQS URL? If I use for e.g https://sqs.us-east-1.amazonaws.com/<account_id>/<my_queue_name> in SDK v1 and sqs.us-east-1.amazonaws.com is my Private DNS name for the VPC endpoint. Does that mean I don't have to set the endpoint in the SQS client of SDK and it can be deduced from the SQS URL itself? and it will not use the default service endpoint although it's same as the private DNS name
I can't say how individual libraries will determine the endpoint even if it can be determined from the service URL (other services don't work that way). In general private endpoints have to be explicitly specified to the library.