- 最新
- 投票最多
- 评论最多
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.
Hi rslak,
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,
Jackie
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:
$ aws sqs receive-message --queue-url "https://sqs.eu-central-1.amazonaws.com/<my_queue_name>" --max-number-of-messages 1
Connect timeout on endpoint URL: "https://eu-central-1.queue.amazonaws.com/"
I am using default VPC security group with everything open.
I will try with CloudFormation example.
相关内容
- AWS 官方已更新 1 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
Nailed it for me! Great!
Could you explain in a little more detail what you mean by this? Thanks.