<?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: Does deploying Splunk from AWS require a public IP address? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Does-deploying-Splunk-from-AWS-require-a-public-IP-address/m-p/183430#M52810</link>
    <description>&lt;P&gt;How are you accessing this system via ssh or remote desktop?  Do you have a direct connection into your AWS instance (VPC or dedicated connection)?  If you cannot connect to the instance, then you need to use a public IP.&lt;/P&gt;

&lt;P&gt;If you do have access to your AWS instance, then simply run a &lt;CODE&gt;netstat -an |grep 8000&lt;/CODE&gt; and see if the server is listening on that TCP port.  If you don't see that port listed, then you'll probably need to make sure splunk is running &lt;CODE&gt;ps -ef |grep splunk&lt;/CODE&gt; or &lt;CODE&gt;$SPLUNK_HOME/bin/splunk -status&lt;/CODE&gt; .  &lt;/P&gt;

&lt;P&gt;Lastly, if you are running iptables on this instance, make sure it's setup to allow for communication on port 8000.&lt;/P&gt;</description>
    <pubDate>Tue, 30 Jun 2015 16:09:23 GMT</pubDate>
    <dc:creator>amiracle</dc:creator>
    <dc:date>2015-06-30T16:09:23Z</dc:date>
    <item>
      <title>Does deploying Splunk from AWS require a public IP address?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Does-deploying-Splunk-from-AWS-require-a-public-IP-address/m-p/183429#M52809</link>
      <description>&lt;P&gt;I deployed Splunk Enterprise appliance from AWS Marketplace. The Splunk is deployed, but I cannot access the URL X.X.X.X:8000&lt;BR /&gt;
I have all the ports opened.&lt;BR /&gt;
The only difference is I didn't assign a public IP address.&lt;BR /&gt;
Is a public IP address required for Splunk appliance?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2015 05:44:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Does-deploying-Splunk-from-AWS-require-a-public-IP-address/m-p/183429#M52809</guid>
      <dc:creator>Beaubeau</dc:creator>
      <dc:date>2015-06-30T05:44:06Z</dc:date>
    </item>
    <item>
      <title>Re: Does deploying Splunk from AWS require a public IP address?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Does-deploying-Splunk-from-AWS-require-a-public-IP-address/m-p/183430#M52810</link>
      <description>&lt;P&gt;How are you accessing this system via ssh or remote desktop?  Do you have a direct connection into your AWS instance (VPC or dedicated connection)?  If you cannot connect to the instance, then you need to use a public IP.&lt;/P&gt;

&lt;P&gt;If you do have access to your AWS instance, then simply run a &lt;CODE&gt;netstat -an |grep 8000&lt;/CODE&gt; and see if the server is listening on that TCP port.  If you don't see that port listed, then you'll probably need to make sure splunk is running &lt;CODE&gt;ps -ef |grep splunk&lt;/CODE&gt; or &lt;CODE&gt;$SPLUNK_HOME/bin/splunk -status&lt;/CODE&gt; .  &lt;/P&gt;

&lt;P&gt;Lastly, if you are running iptables on this instance, make sure it's setup to allow for communication on port 8000.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2015 16:09:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Does-deploying-Splunk-from-AWS-require-a-public-IP-address/m-p/183430#M52810</guid>
      <dc:creator>amiracle</dc:creator>
      <dc:date>2015-06-30T16:09:23Z</dc:date>
    </item>
  </channel>
</rss>

