Skip to content
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] Add option for S3 input to work without SQS notification #18205

Closed
kaiyan-sheng opened this issue May 4, 2020 · 10 comments · Fixed by #27332
Closed

[Filebeat] Add option for S3 input to work without SQS notification #18205

kaiyan-sheng opened this issue May 4, 2020 · 10 comments · Fixed by #27332
Assignees
Labels
enhancement size/L Team:Platforms Label for the Integrations - Platforms team

Comments

@kaiyan-sheng
Copy link
Contributor

Current S3 input in Filebeat relies on SQS to send notification when a new log message is stored in S3 bucket. Some users only want a simple polling method applied on the S3 bucket periodically without SQS, similar to Logstash s3 input .

This will be very useful especially for users who don't need near real-time log message collection. The setup will be a lot simpler without SQS involved.

This idea is brought up in discuss forum issue https://discuss.elastic.co/t/aws-vpcflow-errors-count-not-find-region-configuration-context-deadline-exceeded.

@kaiyan-sheng kaiyan-sheng added the Team:Platforms Label for the Integrations - Platforms team label May 4, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-platforms (Team:Platforms)

@kaiyan-sheng
Copy link
Contributor Author

@mukeshelastic I would love to get your opinion on this. Thank you!!

@kaiyan-sheng kaiyan-sheng added the discuss Issue needs further discussion. label May 4, 2020
@kaiyan-sheng
Copy link
Contributor Author

Note: If we decide to implement this, then the current s3 input probably will be renamed to s3-sqs input instead.

@andresrc andresrc added [zube]: Backlog and removed [zube]: Inbox discuss Issue needs further discussion. labels May 12, 2020
@kaiyan-sheng
Copy link
Contributor Author

We might have to wait till #15324 is done before start working on this one.

@jamiehynds
Copy link

@kaiyan-sheng we recently shipped a Cisco Umbrella integration which leverages the Beats S3 input. This works fine for Umbrella customers using self-managed S3 buckets, but Cisco also provide Cisco-managed buckets where SQS notifications are not available. It looks like we don't be able to support Cisco-managed buckets until this issue is address.

/cc @P1llus

@P1llus
Copy link
Member

P1llus commented Nov 26, 2020

There is certainly needs and usecases for this indeed! Custom log sources could be fetched with Logstash, but if we want to build modules that store their data on a S3 bucket without a SQS queue we do indeed need that option.

@aspacca
Copy link

aspacca commented Jul 15, 2021

@kaiyan-sheng

Note: If we decide to implement this, then the current s3 input probably will be renamed to s3-sqs input instead.

Do we need a different input or can we use the same input relying either queue_url or s3_bucket is set in the config?

@kaiyan-sheng
Copy link
Contributor Author

@aspacca I prefer using the same input aws-s3 and just adding a new config. WDYT?

@aspacca
Copy link

aspacca commented Jul 15, 2021

@kaiyan-sheng totally agree

@LaZyDK
Copy link
Contributor

LaZyDK commented Jul 27, 2021

This will allow Filebeat to pull Cisco Umbrella logs from a Cisco Managed S3 bucket. This is also possible with Logstash today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement size/L Team:Platforms Label for the Integrations - Platforms team
Projects
None yet
8 participants