# Run remote commands from DevTools

**URL:** <https://discuss.elastic.co/t/run-remote-commands-from-devtools/168290>\
**Category:** Elasticsearch\
**Tags:** ccs-cross-cluster-search\
**Created:** [February 13, 2019, 8:48pm UTC](https://discuss.elastic.co/t/run-remote-commands-from-devtools/168290 "2019-02-13T20:48:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rmsys](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rmsys/32/40932_2.png) [@rmsys](https://discuss.elastic.co/u/rmsys)\
**Post date:** [February 13, 2019, 8:48pm UTC](https://discuss.elastic.co/t/run-remote-commands-from-devtools/168290/1 "2019-02-13T20:48:46Z")

</div>

Hi

I configured out this scenario

cluster: lab

- client-node
- data-node
- master-node

cluster: kibana-lab

- els + kibana (localhost)
- remote cluster config

When a run command 'GET /\_remote/info' from DevTools in kibana, I received the correct result;

When a run 'GET /cluster\_data:netflix/\_search' from DevTools in kibana, I received the correct result too;

But, when I tried create a index on remote cluster I received this error:

1. 

> PUT /cluster\_data/shakespeare { "mappings": { "doc": { "properties": { "speaker": {"type": "keyword"}, "play\_name": {"type": "keyword"}, "line\_id": {"type": "integer"}, "speech\_number": {"type": "integer"} } } }}

```
{
  "error": "Incorrect HTTP method for uri [/cluster_data/shakespeare?pretty] and method [PUT], allowed: [POST]",
  "status": 405
}

```

1. 

> PUT /cluster\_data:shakespeare/ { "mappings": { "doc": { "properties": { "speaker": {"type": "keyword"}, "play\_name": {"type": "keyword"}, "line\_id": {"type": "integer"}, "speech\_number": {"type": "integer"} } } }}

```
#! Deprecation: index or alias name [cluster_data:shakespeare] containing ':' is deprecated. Elasticsearch 7.x will read, but not allow creation of new indices containing ':'
#! Deprecation: the default number of shards will change from [5] to [1] in 7.0.0; if you wish to continue using the default of [5] shards, you must manage this on the create index request or with an index template
{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "index" : "cluster_data:shakespeare"
}

```

But, this is created in kibana-cluster...

**So, is possible make this?**

---

<div class="post-metadata">

**Author:** ![rmsys](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rmsys/32/40932_2.png) [@rmsys](https://discuss.elastic.co/u/rmsys)\
**Post date:** [February 21, 2019, 5:37pm UTC](https://discuss.elastic.co/t/run-remote-commands-from-devtools/168290/2 "2019-02-21T17:37:51Z")

</div>

bump

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [February 21, 2019, 7:31pm UTC](https://discuss.elastic.co/t/run-remote-commands-from-devtools/168290/3 "2019-02-21T19:31:59Z")

</div>

As far as I know cross-cluster search only exposes search APIs and not system APIs. This is why you can search but not create indices or get remote cluster statistics.

---

<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 21, 2019, 7:32pm UTC](https://discuss.elastic.co/t/run-remote-commands-from-devtools/168290/4 "2019-03-21T19:32:04Z")

</div>

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