# Elastic Security: Strategies for Analyzing Large Files (Over 500MB)

**URL:** <https://discuss.elastic.co/t/elastic-security-strategies-for-analyzing-large-files-over-500mb/373253>\
**Category:** Elastic Security\
**Created:** [January 15, 2025, 10:32pm UTC](https://discuss.elastic.co/t/elastic-security-strategies-for-analyzing-large-files-over-500mb/373253 "2025-01-15T22:32:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Illya\_Bjazevic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/illya_bjazevic/32/139677_2.png) [@Illya\_Bjazevic](https://discuss.elastic.co/u/Illya_Bjazevic)\
**Post date:** [January 15, 2025, 10:32pm UTC](https://discuss.elastic.co/t/elastic-security-strategies-for-analyzing-large-files-over-500mb/373253/1 "2025-01-15T22:32:53Z")

</div>

I am new to Elastic. I discovered that with the File Data Visualizer, we can upload files up to 500MB. Is there an "official" strategy to analyze larger files, such as dividing the data into chunks and later combining them within Elastic using SQL, or uploading the file to AWS S3 and connecting Elastic to it? For now, I am focused on the machine learning aspect of Elastic Security, and I am wondering how to analyze jobs that require older data. Sometimes, data is automatically moved to AWS S3 or other storage solutions to reduce costs. Thank you for everything!

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/9/99a3373bc4da9c10a97024a4bee3f5d1fb363f04.png)

---

<div class="post-metadata">

**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\
**Post date:** [January 15, 2025, 10:36pm UTC](https://discuss.elastic.co/t/elastic-security-strategies-for-analyzing-large-files-over-500mb/373253/2 "2025-01-15T22:36:19Z")

</div>

@Illya_Bjazevic , you can bump that up to 1GB via the Kibana advanced settings:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/1/8176ef79b5f2790e2a95c815193d608b99efab08.png)

Otherwise, you simply ingest any file, of any size, using Elastic Agent and the Custom Log integration.

---

<div class="post-metadata">

**Author:** ![Illya\_Bjazevic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/illya_bjazevic/32/139677_2.png) [@Illya\_Bjazevic](https://discuss.elastic.co/u/Illya_Bjazevic)\
**Post date:** [January 16, 2025, 2:45am UTC](https://discuss.elastic.co/t/elastic-security-strategies-for-analyzing-large-files-over-500mb/373253/3 "2025-01-16T02:45:24Z")

</div>

Awesome! Thanks for the fast help!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 13, 2025, 2:45am UTC](https://discuss.elastic.co/t/elastic-security-strategies-for-analyzing-large-files-over-500mb/373253/4 "2025-02-13T02:45:57Z")

</div>

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