# Elasticsearch data in another storage server

**URL:** <https://discuss.elastic.co/t/elasticsearch-data-in-another-storage-server/205459>\
**Category:** Elasticsearch\
**Created:** [October 28, 2019, 12:30pm UTC](https://discuss.elastic.co/t/elasticsearch-data-in-another-storage-server/205459 "2019-10-28T12:30:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![morita](https://avatars.discourse-cdn.com/v4/letter/m/f9ae1b/32.png) [@morita](https://discuss.elastic.co/u/morita)\
**Post date:** [October 28, 2019, 12:30pm UTC](https://discuss.elastic.co/t/elasticsearch-data-in-another-storage-server/205459/1 "2019-10-28T12:30:50Z")

</div>

hi, I wonder can I use data nodes with sufficient CPU and Ram for indexing documents then save them in another storage server?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [October 31, 2019, 1:13pm UTC](https://discuss.elastic.co/t/elasticsearch-data-in-another-storage-server/205459/2 "2019-10-31T13:13:00Z")

</div>

no, data nodes will always store the data. If you want to change documents and their structure before indexing, there is a feature called [ingest node](https://www.elastic.co/guide/en/elasticsearch/reference/7.4/ingest.html), that you may want to take a look at, as this enrichment can happen on dedicated nodes.

Can you explain your use-case a bit more, and what exactly you are after?

---

<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:** [November 28, 2019, 1:13pm UTC](https://discuss.elastic.co/t/elasticsearch-data-in-another-storage-server/205459/3 "2019-11-28T13:13:17Z")

</div>

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