# Querying for remote indexes via cross cluster search

**URL:** https://discuss.elastic.co/t/querying-for-remote-indexes-via-cross-cluster-search/131754
**Category:** Elasticsearch
**Created:** [May 14, 2018, 2:05pm UTC](https://discuss.elastic.co/t/querying-for-remote-indexes-via-cross-cluster-search/131754 "2018-05-14T14:05:17Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![bbailey](https://avatars.discourse-cdn.com/v4/letter/b/ebca7d/32.png) [@bbailey](https://discuss.elastic.co/u/bbailey)
#### Post date: [May 14, 2018, 2:05pm UTC](https://discuss.elastic.co/t/querying-for-remote-indexes-via-cross-cluster-search/131754/1 "2018-05-14T14:05:17Z")

</div>

Sorry of this is a dumb question but my expectation is that despite switching from tribe nodes to cross cluster search nodes I should be able to query all the names of my remote indices using a browser.

It seems that is not the case and wondered if there is obvious solution

I know that my configuration is OK as a simple aggregation entered in my browser works  
`http://search01:9200/*:log-*/_count`  
count 469112464

But this query returns nothing  
`http://search01:9200/*:log-*`

and this query returns local indices on the css search node  
`http://search01:9200/*`

When we were using tribe nodes then this query would give me a list of all the indices.

---

<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: [June 11, 2018, 2:05pm UTC](https://discuss.elastic.co/t/querying-for-remote-indexes-via-cross-cluster-search/131754/2 "2018-06-11T14:05:23Z")

</div>

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