Filebeat AWS Module S3 input error queueURL is not in format

Trying to use filebeat to monitor my AWS resources in ISO environment. It looks like the AWS standard endpoint is hard coded.

my filebeat.yml

- type: s3
  visibility_timeout: 300s


ERROR	[s3]	s3/input.go:93 Input 'S3' failed with: getRegionFromQueueURL failed: queueURL is not in format: https://sqs.{REGION_ENDPOINT}{ACCOUNT_NUMBER}/{QUEUE_NAME} 

I am also behind a proxy and dont see the traffic hitting the proxy server, not sure if this is related.

Anything on this???


I think you are right. For some reason the Module expects to find the URL in this format. beats/collector.go at 616266fa286f0ac4408348fcd4da7da2358182b1 · elastic/beats · GitHub

I'm not sure what would be different with your case or if it's just that the URL format is different. Most probably we just need to adjust the code so as to cover cases like yours.

@Kaiyan_Sheng do you think this would be an enhancement request?

Yeah it looks like it is hardcoded to only work if the endpoint is in AWS Commercial with as the endpoint, it looks for that in the code. we would need it to be a variable so instead of looking for say
It should be something like
Allowing you to set the endpoint to whatever AWS ENV you are in so in our case
This is probably also hurting the people in Gov cloud and anything else that does not point to

@cjm3625 Hey sorry I just saw the message!! Yep this looks like a bug to me! We do have endpoint config parameter to use but I think there is still a bug there to abstract region name from the queue URL. Do you mind creating a github issue for this please?

Sure, how do I go about doing that?

Here is the link: Thank you!!

Gov cloud wont be affected by this because its just different region names, but still the domain. I just submitted a draft PR that i think will resolve the issue, [Filebeat] Fix hardcoded endpoint by legoguy1000 · Pull Request #24861 · elastic/beats · GitHub.

1 Like

The PR has been merged and will be in 7.13 and is targeted for 7.12.1 as well.

1 Like

@cjm3625 have u been able to upgrade to 7.12.1+ to see if this solved your issue?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.