# Elastic.co new cluster: set reindex.remote.whitelist

**URL:** <https://discuss.elastic.co/t/elastic-co-new-cluster-set-reindex-remote-whitelist/121947>\
**Category:** Elasticsearch\
**Created:** [February 28, 2018, 10:08pm UTC](https://discuss.elastic.co/t/elastic-co-new-cluster-set-reindex-remote-whitelist/121947 "2018-02-28T22:08:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ar21](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@ar21](https://discuss.elastic.co/u/ar21)\
**Post date:** [February 28, 2018, 10:08pm UTC](https://discuss.elastic.co/t/elastic-co-new-cluster-set-reindex-remote-whitelist/121947/1 "2018-02-28T22:08:51Z")

</div>

I am trying to upgrade from ES 2.4 to 6.2 using the "reindex from remote" approach. I am using [elastic.co](http://elastic.co) hosted service for the existing 2.4 cluster. I am trying to create a new 6.2 cluster, also on [elastic.co](http://elastic.co). If I set `reindex.remote.whitelist` in user settings when creating the new cluster using the UI, it says "Illegal User Settings". How do I proceed?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 28, 2018, 10:29pm UTC](https://discuss.elastic.co/t/elastic-co-new-cluster-set-reindex-remote-whitelist/121947/2 "2018-02-28T22:29:39Z")

</div>

Please see [https://www.elastic.co/cloud/as-a-service/support](https://www.elastic.co/cloud/as-a-service/support) on how to raise a support ticket for Elastic Cloud 🙂

---

<div class="post-metadata">

**Author:** ![ar21](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@ar21](https://discuss.elastic.co/u/ar21)\
**Post date:** [March 2, 2018, 1:16am UTC](https://discuss.elastic.co/t/elastic-co-new-cluster-set-reindex-remote-whitelist/121947/3 "2018-03-02T01:16:16Z")

</div>

Contacted elastic support and got the answer. I don't really need to set it, since the default setting (as mentioned [here](https://www.elastic.co/guide/en/cloud/current/cluster-config.html#user-settings) ) allows remote indexing from any `.io` or `.com` domain.

Also, I was setting it like this:  
`reindex.remote.whitelist 9279bc1b294df7e40fc07f9b7f9f683.us-west-2.aws.found.io:9243`  
but taking hint from the guide page, the correct setting is probably like this:  
`reindex.remote.whitelist ["9279bc1b294df7e40fc07f9b7f9f683.us-west-2.aws.found.io:9243"]`

---

<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:** [March 30, 2018, 1:16am UTC](https://discuss.elastic.co/t/elastic-co-new-cluster-set-reindex-remote-whitelist/121947/4 "2018-03-30T01:16:28Z")

</div>

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