# Reindex from remote (AWS Service) **URL:** \ **Category:** Elasticsearch\ **Created:** [April 17, 2017, 7:23pm UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616 "2017-04-17T19:23:20Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![danilo.akamine](https://avatars.discourse-cdn.com/v4/letter/d/77aa72/32.png) [@danilo.akamine](https://discuss.elastic.co/u/danilo.akamine)\ **Post date:** [April 17, 2017, 7:23pm UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616/1 "2017-04-17T19:23:21Z")
I'm running a Amazon Elasticsearch Service 5.1 (last version available there). I'd like to reindex my documents from a remote server, but I can't do this on AWS because I can't modify the elasticsearch.yml file. AWS Elastic Service doesn't provide a way to put **reindex.remote.whitelist** flag in his config. What should I do? Thanks ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [April 17, 2017, 7:41pm UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616/2 "2017-04-17T19:41:04Z")
Unfortunately, I'm afraid that's a rather strict requirement of the `_reindex` API. You will not be able to use `_reindex` to accomplish this task. You can, however, create your own script to pull from one source using the scroll API, and then send all the documents found to the target cluster. It would be a rather manual process, I'm afraid. ---
**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:** [April 17, 2017, 7:43pm UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616/3 "2017-04-17T19:43:24Z")
Can you try with this API? [https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-update-settings.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-update-settings.html) ---
**Author:** ![danilo.akamine](https://avatars.discourse-cdn.com/v4/letter/d/77aa72/32.png) [@danilo.akamine](https://discuss.elastic.co/u/danilo.akamine)\ **Post date:** [April 17, 2017, 7:57pm UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616/4 "2017-04-17T19:57:18Z")
Yes @dadoonet, but it doesn't work. There is a topic about this where a contributor explains why it shouldn't work: > [@Possibility of modifying "reindex.remote.whitelist" via API call?](https://discuss.elastic.co/t/possibility-of-modifying-reindex-remote-whitelist-via-api-call/74693): > > Would it be possible to have the "reindex.remote.whitelist" setting modifiable via the HTTP API instead of having to specify it in the elasticsearch.yml config? I realize this setting currently most likely requires a cluster restart, although it would be great if this could simply be implemented as a settings lookup each time the "/\_reindex" endpoint is called. If you agree and this is a reasonable request, I'd gladly create an issue in the github project to have the included in a future versi… ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [April 17, 2017, 7:58pm UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616/5 "2017-04-17T19:58:51Z")
@dadoonet, the [documentation says it must be in the `elasticsearch.yml`](https://www.elastic.co/guide/en/elasticsearch/reference/5.3/docs-reindex.html) file: > Remote hosts have to be explicitly whitelisted in elasticsearch.yaml using the `reindex.remote.whitelist` property. It can be set to a comma delimited list of allowed remote `host` and `port` combinations (e.g. `otherhost:9200`, `another:9200`, `127.0.10.*:9200`, `localhost:*`). Scheme is ignored by the whitelist - only host and port are used. I think that's by design, that it must be hard-coded before startup. ---
**Author:** ![danilo.akamine](https://avatars.discourse-cdn.com/v4/letter/d/77aa72/32.png) [@danilo.akamine](https://discuss.elastic.co/u/danilo.akamine)\ **Post date:** [April 17, 2017, 8:04pm UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616/6 "2017-04-17T20:04:42Z")
Thanks for suggestion, but I was trying to avoid that. 😞 ---
**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:** [April 17, 2017, 8:43pm UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616/7 "2017-04-17T20:43:31Z")
Of course! I was dumb when I thought about that. Totally insecure proposal but thankfully rejected by elasticsearch 🙂 I wonder if #cloud supports defining this in elasticsearch.yml file BTW. ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [April 18, 2017, 3:33am UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616/8 "2017-04-18T03:33:54Z")
> [@dadoonet](#): > > I wonder if #cloud supports defining this in elasticsearch.yml file BTW. It does. Scroll down to the bottom of the page [here](https://www.elastic.co/guide/en/cloud/current/cluster-config.html) to see it listed, specifically. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 16, 2017, 3:45am UTC](https://discuss.elastic.co/t/reindex-from-remote-aws-service/82616/9 "2017-05-16T03:45:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.