title: How to use elasticsearch or Kibana console in AWS
body: <p>Maybe it is simple question since cannot find anything regarding this. I am following <a href="https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-aws-integrations.html#es-aws-integrations-s3-lambda-es" rel="nofollow noreferrer">https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-aws-integrations.html#es-aws-integrations-s3-lambda-es</a> guide which talks about creating a lambda function that sends s3 data to es.</p>
  
  <p>I've followed all the steps and at checking stage. I've uploaded my sample.log file to s3 and want to check if it had been successfully added to elasticsearch.</p>
  
  <p>I cannot access it from cmd or anaconda prompt using curl</p>
  
  <pre><code>curl GET "https://path/lambda-index/_search?pretty"
  </code></pre>
  
  <p>outputs 
  <code>curl: (5) Could not resolve proxy: GET</code></p>
  
  <p>and </p>
  
  <pre><code>curl GET "https://path/lambda-index/_search?pretty"
  </code></pre>
  
  <p>outputs </p>
  
  <pre><code>curl: (6) Could not resolve host: GET
  curl: (7) Failed to connect to vpc-es-logs-wxmypa5bsx4dqutl7h46qsl3qa.ap-northeast-2.es.amazonaws.com port 443: Timed out
  </code></pre>
  
  <p>I want to now use elasticsearch console or kibana however I do not know how to access it. I've tried going to VPC endpoint and Kibana url posted in elasticsearch domain page and it won't connect.</p>
  
  <p>How can I use es console?</p>
  
  <p><strong>Solved :</strong> After creating new domain with public access it works fine. I guess there were something wrong with VPC, not sure why though(if anyone does know, please explain)</p>