<?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: Splunk Cloud IP range in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunk-Cloud-IP-range/m-p/130100#M3935</link>
    <description>&lt;P&gt;On large Splunkcloud deployments, use an nslookup on your search-head, and you will have the IP.&lt;BR /&gt;
example :  nslookup megazilla.splunkcloud.com&lt;BR /&gt;
if you have several search-heads, use sh1.megazilla.splunkcloud.com sh2.megazilla.splunkcloud.com etc...&lt;/P&gt;

&lt;P&gt;Remark : this does not apply to self service splunkcloud instances, as they use your splunk.com username for the authentication, and cannot use LDAP&lt;/P&gt;

&lt;P&gt;For your indexers, use the same technique with the 5 dns load balanced addresses:&lt;BR /&gt;
nslookup inputs1.megazilla.splunkcloud.com&lt;BR /&gt;
nslookup inputs2.megazilla.splunkcloud.com&lt;BR /&gt;
nslookup inputs3.megazilla.splunkcloud.com&lt;BR /&gt;
nslookup inputs4.megazilla.splunkcloud.com&lt;BR /&gt;
nslookup inputs5.megazilla.splunkcloud.com&lt;/P&gt;

&lt;P&gt;.&lt;/P&gt;</description>
    <pubDate>Fri, 11 Sep 2015 14:58:03 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2015-09-11T14:58:03Z</dc:date>
    <item>
      <title>Splunk Cloud IP range</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Cloud-IP-range/m-p/130098#M3933</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;We are in the process of moving from Splunk on premise to Splunk Cloud and we need to configure LDAPS authentication (such a shame ADFS or SAML aren't supported!).&lt;BR /&gt;
This requires we open up LDAPS on our firewall and for obvious reasons we want to limit this to only the IP's used by Splunk Cloud.  Can anyone confirm these please?&lt;/P&gt;

&lt;P&gt;Many thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2014 13:25:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Cloud-IP-range/m-p/130098#M3933</guid>
      <dc:creator>jodyglsi</dc:creator>
      <dc:date>2014-11-24T13:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud IP range</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Cloud-IP-range/m-p/130099#M3934</link>
      <description>&lt;P&gt;Contact Splunk Cloud Ops support and get the IPs of your Search Heads, and supporting management servers. Only your search heads should have direct user access. When you setup ldap.conf you will need to specify the secure port. Use good SSL certificates to complete the connection. &lt;/P&gt;</description>
      <pubDate>Tue, 01 Sep 2015 14:16:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Cloud-IP-range/m-p/130099#M3934</guid>
      <dc:creator>mcronkrite</dc:creator>
      <dc:date>2015-09-01T14:16:08Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud IP range</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Cloud-IP-range/m-p/130100#M3935</link>
      <description>&lt;P&gt;On large Splunkcloud deployments, use an nslookup on your search-head, and you will have the IP.&lt;BR /&gt;
example :  nslookup megazilla.splunkcloud.com&lt;BR /&gt;
if you have several search-heads, use sh1.megazilla.splunkcloud.com sh2.megazilla.splunkcloud.com etc...&lt;/P&gt;

&lt;P&gt;Remark : this does not apply to self service splunkcloud instances, as they use your splunk.com username for the authentication, and cannot use LDAP&lt;/P&gt;

&lt;P&gt;For your indexers, use the same technique with the 5 dns load balanced addresses:&lt;BR /&gt;
nslookup inputs1.megazilla.splunkcloud.com&lt;BR /&gt;
nslookup inputs2.megazilla.splunkcloud.com&lt;BR /&gt;
nslookup inputs3.megazilla.splunkcloud.com&lt;BR /&gt;
nslookup inputs4.megazilla.splunkcloud.com&lt;BR /&gt;
nslookup inputs5.megazilla.splunkcloud.com&lt;/P&gt;

&lt;P&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2015 14:58:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Cloud-IP-range/m-p/130100#M3935</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2015-09-11T14:58:03Z</dc:date>
    </item>
  </channel>
</rss>

