Skip to content
Discussion options

You must be logged in to vote

There are two problems with this configuration:

  1. The source's endpoint needs a URL scheme, for example https://obs.cn-north-4.myhuaweicloud.com.
  2. In Vector 0.60.0, the aws_s3 source passes that same endpoint to both its S3 and SQS clients. sqs.queue_url identifies the queue but does not override the SQS client's endpoint. Adding the scheme alone therefore still sends SQS requests to your object-storage service, rather than ElasticMQ.

I reproduced this with Vector 0.60.0 and two local HTTP mock servers: all SQS ReceiveMessage requests reached the configured endpoint, and none reached the server named in queue_url. A separate sqs.endpoint setting is currently rejected as an unknown field.

S…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by pront
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
domain:config Anything related to configuring Vector provider:aws Anything `aws` service provider related source:aws_s3 Anything `aws_s3` source related
2 participants