# Confluence Connector for internal, behind VPN Server

**URL:** <https://discuss.elastic.co/t/confluence-connector-for-internal-behind-vpn-server/257261>\
**Category:** Elastic Search\
**Tags:** elastic-workplace-search\
**Created:** [December 1, 2020, 6:24pm UTC](https://discuss.elastic.co/t/confluence-connector-for-internal-behind-vpn-server/257261 "2020-12-01T18:24:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![WHoopes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/whoopes/32/80046_2.png) [@WHoopes](https://discuss.elastic.co/u/WHoopes)\
**Post date:** [December 1, 2020, 6:24pm UTC](https://discuss.elastic.co/t/confluence-connector-for-internal-behind-vpn-server/257261/1 "2020-12-01T18:24:58Z")

</div>

We have a Confluence Server behind a VPN, and are using the cloud hosted Elastic Workplace Search. Is it possible to run the Confluence Connector separately from the Cloud hosted ES stack, and forward data to the cloud hosted ES stack? If not, what are my options for indexing our Confluence data?

---

<div class="post-metadata">

**Author:** ![MadsOhm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madsohm/32/69154_2.png) [@MadsOhm](https://discuss.elastic.co/u/MadsOhm)\
**Post date:** [December 2, 2020, 9:20am UTC](https://discuss.elastic.co/t/confluence-connector-for-internal-behind-vpn-server/257261/2 "2020-12-02T09:20:07Z")

</div>

You could run an additional instance of Workplace Search within your VPN and have it connect to the same Elasticsearch on Cloud. I don't know how well this will work, as you would have two instances competing for being the Confluence connector, so half of the times it will fail (if it cannot connect to Confluence)

Another option is to use the [Custom API Source](https://www.elastic.co/guide/en/workplace-search/current/workplace-search-custom-api-sources.html) to push data to Workplace Search. Here you would have to create your own connector for Confluence using their APIs.

---

<div class="post-metadata">

**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\
**Post date:** [December 2, 2020, 8:43pm UTC](https://discuss.elastic.co/t/confluence-connector-for-internal-behind-vpn-server/257261/3 "2020-12-02T20:43:02Z")

</div>

Yet another option, you could just use Elastic Cloud to host Elasticsearch, and host just a single instance of Enterprise Search inside your VPN.

---

<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:** [October 31, 2022, 2:48am UTC](https://discuss.elastic.co/t/confluence-connector-for-internal-behind-vpn-server/257261/4 "2022-10-31T02:48:06Z")

</div>

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