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

[Amazon Security Lake] Parquet File Support #506

Open
jamiehynds opened this issue Oct 26, 2023 · 0 comments
Open

[Amazon Security Lake] Parquet File Support #506

jamiehynds opened this issue Oct 26, 2023 · 0 comments

Comments

@jamiehynds
Copy link

jamiehynds commented Oct 26, 2023

Describe the enhancement:
Amazon Security Lake can store security telemetry from both AWS services and 3rd parties such as CrowdStrike, Zscaler and many more. Data is stored in Apache Parquet files. We have an existing integration to ingest this data from Security Lake and map it to ECS to ensure it can be leveraged within Elastic Security.

Our current integration relies upon Elastic Agent, but we see a strong demand amongst AWS customers to leverage Serverless Forwarder instead.

Can we add support to Servless Forwarder to read/decode Parquet files, to enable Amazon Security Lake customers to ingest data without the need for Elastic Agent?

PR's to highlight what was done on the Beats S3 input to add Parquet file support: elastic/beats#35183 and elastic/beats#35578

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant