# How to setup curator for multiple clusters?

**URL:** <https://discuss.elastic.co/t/how-to-setup-curator-for-multiple-clusters/135914>\
**Category:** Elasticsearch\
**Created:** [June 14, 2018, 12:29pm UTC](https://discuss.elastic.co/t/how-to-setup-curator-for-multiple-clusters/135914 "2018-06-14T12:29:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vikas\_gopal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_gopal/32/47661_2.png) [@vikas\_gopal](https://discuss.elastic.co/u/vikas_gopal)\
**Post date:** [June 14, 2018, 12:29pm UTC](https://discuss.elastic.co/t/how-to-setup-curator-for-multiple-clusters/135914/1 "2018-06-14T12:29:14Z")

</div>

Hi Experts,

I was wondering if I can set up curator for multiple clusters . Below is my curator configuration which works absolutely fine for one cluster . Now I want to apply same setup for my second cluster which uses different port like 30011 . Please suggest how I can achieve this .

```
client:
  hosts:
    - 10.X.X.X
  port: 20011
  url_prefix:
  use_ssl: False
  certificate:
  client_cert:
  client_key:
  ssl_no_validate: False
  http_auth:
  timeout: 30
  master_only: False
logging:
  loglevel: INFO
  logfile:
  logformat: default
  blacklist: ['elasticsearch', 'urllib3'] 

```

Regards  
VG

---

<div class="post-metadata">

**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:** [June 14, 2018, 12:57pm UTC](https://discuss.elastic.co/t/how-to-setup-curator-for-multiple-clusters/135914/2 "2018-06-14T12:57:41Z")

</div>

You cannot configure one Curator installation to apply to multiple clusters. It does not work like that. Specifying multiple `hosts` round-robins the requests across multiple hosts _within_ a cluster.

You need separate Curator client configurations for each cluster, even if the action definitions are identical across clusters.

---

<div class="post-metadata">

**Author:** ![vikas\_gopal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_gopal/32/47661_2.png) [@vikas\_gopal](https://discuss.elastic.co/u/vikas_gopal)\
**Post date:** [June 20, 2018, 4:31am UTC](https://discuss.elastic.co/t/how-to-setup-curator-for-multiple-clusters/135914/3 "2018-06-20T04:31:44Z")

</div>

Thanks for quick response , so here separate Curator Client config means I need to create separate curator.yml file. SO something like one cluster will use curator.yml and another cluster will use curator1.yml and so on . Please correct me if I am wrong I need to mention a separate path for second config file in the below command

curator [--config /opt/curator/CONFIG.YML] [--dry-run] ACTION\_FILE.YML  
curator [--config /opt/curator/CONFIG1.YML] [--dry-run] ACTION\_FILE.YML

---

<div class="post-metadata">

**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:** [June 20, 2018, 5:04am UTC](https://discuss.elastic.co/t/how-to-setup-curator-for-multiple-clusters/135914/4 "2018-06-20T05:04:48Z")

</div>

That’s correct.

---

<div class="post-metadata">

**Author:** ![vikas\_gopal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_gopal/32/47661_2.png) [@vikas\_gopal](https://discuss.elastic.co/u/vikas_gopal)\
**Post date:** [June 20, 2018, 5:06am UTC](https://discuss.elastic.co/t/how-to-setup-curator-for-multiple-clusters/135914/5 "2018-06-20T05:06:49Z")

</div>

Awesome will try and respond thanks again .

---

<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:** [July 18, 2018, 5:06am UTC](https://discuss.elastic.co/t/how-to-setup-curator-for-multiple-clusters/135914/6 "2018-07-18T05:06:49Z")

</div>

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