<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: HEC token management for HA in Security</title>
    <link>https://community.splunk.com/t5/Security/HEC-token-management-for-HA/m-p/325707#M8364</link>
    <description>&lt;P&gt;Hi @deepashri_123,&lt;/P&gt;

&lt;P&gt;Based on documentation &lt;A href="http://dev.splunk.com/view/event-collector/SP-CAAAE73"&gt;http://dev.splunk.com/view/event-collector/SP-CAAAE73&lt;/A&gt;, &lt;CODE&gt;Note: Using HTTP Event Collector in a distributed deployment is incompatible with indexer clustering. Specifically, cluster peers are not supported as deployment clients.&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;So in this case you require Heavy Forwarders and setup HEC on those machines.&lt;/P&gt;</description>
    <pubDate>Wed, 24 Jan 2018 08:40:08 GMT</pubDate>
    <dc:creator>harsmarvania57</dc:creator>
    <dc:date>2018-01-24T08:40:08Z</dc:date>
    <item>
      <title>HEC token management for HA</title>
      <link>https://community.splunk.com/t5/Security/HEC-token-management-for-HA/m-p/325706#M8363</link>
      <description>&lt;P&gt;Hi Splunkers,&lt;/P&gt;

&lt;P&gt;We have a distributed environment with 2SH, 2 indexers and 1 master.&lt;BR /&gt;
We need to set up HEC with HA. Currently my HEC is available on my indexers. &lt;BR /&gt;
I would like to know if the indexers are restarted will there be data loss ?&lt;/P&gt;

&lt;P&gt;Also what factors to be considered for security?&lt;/P&gt;

&lt;P&gt;Below is a similar question :&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/424299/architecting-ha-in-a-small-hec-http-event-collecto.html"&gt;https://answers.splunk.com/answers/424299/architecting-ha-in-a-small-hec-http-event-collecto.html&lt;/A&gt;&lt;BR /&gt;
Any help would be appreciated!&lt;BR /&gt;
Thanks in advance. &lt;/P&gt;</description>
      <pubDate>Wed, 24 Jan 2018 07:23:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/HEC-token-management-for-HA/m-p/325706#M8363</guid>
      <dc:creator>deepashri_123</dc:creator>
      <dc:date>2018-01-24T07:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: HEC token management for HA</title>
      <link>https://community.splunk.com/t5/Security/HEC-token-management-for-HA/m-p/325707#M8364</link>
      <description>&lt;P&gt;Hi @deepashri_123,&lt;/P&gt;

&lt;P&gt;Based on documentation &lt;A href="http://dev.splunk.com/view/event-collector/SP-CAAAE73"&gt;http://dev.splunk.com/view/event-collector/SP-CAAAE73&lt;/A&gt;, &lt;CODE&gt;Note: Using HTTP Event Collector in a distributed deployment is incompatible with indexer clustering. Specifically, cluster peers are not supported as deployment clients.&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;So in this case you require Heavy Forwarders and setup HEC on those machines.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jan 2018 08:40:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/HEC-token-management-for-HA/m-p/325707#M8364</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2018-01-24T08:40:08Z</dc:date>
    </item>
  </channel>
</rss>

