title: AWS ElasticSearch as a Service fails to connect via standalone KIBANA
body: <p>I have ElasticSearch as a service on AWS. What I have done is installed a 6.1.2 Kibana on a different EC2 Instance and trying to connect it. My Policy are in place and I can browse the endpoint from the EC2 instance.</p>
  <p>However when i change Kibana.yml to point to the endpoint from ES AWS Service it turns RED.</p>
  <h2>AWS ES Endpoint Successful call from the said EC2 where standalone KIBANA is installed</h2>
  <pre><code>{
      &quot;name&quot; : &quot;BBXYZ&quot;,
      &quot;cluster_name&quot; : &quot;XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&quot;,
      &quot;cluster_uuid&quot; : &quot;XXXXXXXXXXXXXXXXXXXXX&quot;,
      &quot;version&quot; : {
      &quot;number&quot; : &quot;6.0.1&quot;,
      &quot;build_hash&quot; : &quot;d951bbf&quot;,
      &quot;build_date&quot; : &quot;2017-12-07T01:43:54.348Z&quot;,
      &quot;build_snapshot&quot; : false,
      &quot;lucene_version&quot; : &quot;7.0.1&quot;,
      &quot;minimum_wire_compatibility_version&quot; : &quot;5.6.0&quot;,
      &quot;minimum_index_compatibility_version&quot; : &quot;5.0.0&quot;
      },
      &quot;tagline&quot; : &quot;You Know, for Search&quot;
  }
  </code></pre>
  <h2>Kibana Version 6.1.2</h2>
  <p>Kibana Error : Status Red
  <strong>plugin:elasticsearch@6.1.2  Request Timeout after 3000ms</strong></p>
  <p>Please help; do i need to have KIBANA AND AWS ES ON THE SAME VERSION. AWS ES IS ON 6.0</p>
  <p>The reason why ui am installing standalone KIBANA is because we want to enable login and disable actions on the KIBANA for few</p>