# Non-interactive Automated Autopsy / Cloud Scaling

**URL:** <https://sleuthkit.discourse.group/t/non-interactive-automated-autopsy-cloud-scaling/3261>\
**Category:** Autopsy Help\
**Created:** [June 2, 2022, 1:12pm UTC](https://sleuthkit.discourse.group/t/non-interactive-automated-autopsy-cloud-scaling/3261 "2022-06-02T13:12:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![autopsy\_user](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@autopsy\_user](https://sleuthkit.discourse.group/u/autopsy_user)\
**Post date:** [June 2, 2022, 1:12pm UTC](https://sleuthkit.discourse.group/t/non-interactive-automated-autopsy-cloud-scaling/3261/1 "2022-06-02T13:12:53Z")

</div>

Hi,

I’d like to create a process for easy scaling of a specific procedure in Autopsy. This would be useful during large Autopsy projects to use AWS/Azure/etc. scaling to control the tradeoff between # of servers working concurrently vs. time to completion.

Ideally, I’d provide a folder path full of logical files to this process, and it would 1) create a case, 2) add that path to the case, 3) ingest and run embedded file extractor, email parser, and keyword search, 4) export the results of the keyword searches to .CSV.

Is there a command line or other automated way of doing these steps in Autopsy/Sleuthkit?

Thanks!

---

<div class="post-metadata">

**Author:** ![jgalbraith](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@jgalbraith](https://sleuthkit.discourse.group/u/jgalbraith)\
**Post date:** [June 9, 2022, 4:54pm UTC](https://sleuthkit.discourse.group/t/non-interactive-automated-autopsy-cloud-scaling/3261/2 "2022-06-09T16:54:46Z")

</div>

What you’re looking for sounds like something Automated Ingest can do([Autopsy User Documentation: Automated Ingest](http://sleuthkit.org/autopsy/docs/user-docs/4.19.3/auto_ingest_page.html)). The scaling of servers will be the hard part as every automated ingest node will need configured.