Issues with SQS custom endpoint setup on Main
per https://github.com/elastic/beats/pull/39709
We need to:
-
[ ] Fix parsing regionname from custom endpoints like
s3.us-east-1.bills.domain.com. See https://github.com/elastic/beats/pull/39709/files#diff-589195ecff44ed2c6bf097da676822765ae86c2e73fc5789aaf0a64d8bb26ff1R349-R377 for an example fix. Should probably go here: https://github.com/elastic/beats/blob/05c5957b23f8099736e4bfa629120b18eb49569f/x-pack/filebeat/input/awss3/sqs.go#L41-L43 -
[ ] Use the default endpoint resolver if the endpoint begins with s3. See: https://github.com/elastic/beats/pull/39709/files#diff-589195ecff44ed2c6bf097da676822765ae86c2e73fc5789aaf0a64d8bb26ff1R78-R92 for an example fix. Should probably go here: https://github.com/elastic/beats/blob/main/x-pack/filebeat/input/awss3/input.go#L51-L60
@faec
Related to https://github.com/elastic/beats/issues/39706 and https://github.com/elastic/beats/pull/39709
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)