Looks like you are using the legacy endpoint format and it is not supported in SQS VPC endpoint. Give https://sqs.eu-central-1.amazonaws.com a try. (detailed endpoint information per region can be found here: https://docs.aws.amazon.com/general/latest/gr/rande.html#sqs_region)
It is also possible that you have restricted traffic and access in the security group assigned to your VPC endpoint. I would recommend you to follow our tutorial: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-sending-messages-from-vpc.html, setup a functional example, and then compare and constrast the differences.
Hope this helps,
Thanks for suggestions.
I have tried with provided endpoint but without luck. I still get the same error, although I have changed the endpoint name:
I am using default VPC security group with everything open.
I will try with CloudFormation example.
I have identified the problem.
It was security group. I have to to set up separate group where all traffic destination/source has range of internal subnet and not just everything.
SQS VPC interface endpoint and it's usage via AWS SDK v1asked 4 months ago
What do I need to allow for my Security group to receive inbound traffic from SQS in lambda?
SQS interface endpoint for cross region accessAccepted Answerasked 2 years ago
Can lambdas inside a private subnet still receive data from SQS ?
How can Ec2 Instance in private subnet access internet via vpc endpoint?Accepted Answerasked 5 months ago
Pushing to SQS through VPC Endpoint from lambda in private VPC failsasked a year ago
Can not access SQS via VPC SQS endpointasked 4 years ago
How can I prevent an Amazon SQS message from invoking my Lambda function more than once?EXPERTasked a year ago
Do we need VPC Endpoints for SNS and SQS if data not originating from any VPC and directly landing in SNS from external sourceasked 10 months ago
Reading SQS Message via Listenerasked 7 months ago