-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Filebeat] Enable S3 support for other clouder than AWS's #28222
Comments
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Pinging @elastic/integrations (Team:Integrations) |
2024-02-26 17:07:12 {"log.level":"error","@timestamp":"2024-02-26T11:37:12.158Z","log.origin":{"function":"github.com/elastic/beats/v7/libbeat/cmd/instance.handleError","file.name":"instance/beat.go","file.line":1315},"message":"Exiting: error initializing publisher: output type s3 undefined","service.name":"filebeat","ecs.version":"1.6.0"} can i get the possible reason for getting this error? |
@premeximietas , please ask for this kind of troubleshooting question in the forum https://discuss.elastic.co/c/observability/logs/69 :) Please provide details about your setup, thanks 👍 |
Describe the enhancement:
Many cloud service and private resources handle s3.
Most s3 libs support such alternate s3 services, like logstash
Since bucket_arn feature, SQS isn't a dependency anymore so using any S3 should be possible.
Describe a specific use case for the enhancement or feature:
Well i'd love to retrieve logs stored to Scaleway S3 buckets.
I didn't manage to use https://s3.fr-par.scw.cloud s3-compat endpoint with filebeat, whearus using it with logstash or vector.dev is possible
The text was updated successfully, but these errors were encountered: