CODEWITHSUNDEEP
amazon-web-serviceselasticsearchkibana
po5i
po5i

Reputation: 558

How to setup an own Kibana client over aws ES service

I deployed an ES service 5.1 over AWS. The access policy is restricted to a unique IP. This public IP belongs to a EC2 instance (red hat).

At the EC2 instance, I installed kibana 5.1.2 using yum and I configured the kibana.yml as follows:

server.host: "ec2-x-x-x-x.us-west-2.compute.amazonaws.com"
server.name: "my-kibana"
elasticsearch.url: "http://my-es-domain-xxxxxxxxxxxx.us-west-2.es.amazonaws.com"

The rest config remains untouched.

With the EC2 instance I can do cURL requests over my ES with no problem (I had created an index, add some documents and search). But Kibana is giving me this error:

ui settings  Elasticsearch plugin is red
plugin:[email protected]  Ready
plugin:[email protected]   Request Timeout after 3000ms
plugin:[email protected]     Ready
plugin:[email protected]    Ready

So I can't use my Kibana client. Can you tell what's missing?

Thanks.

Upvotes: 3

Views: 2548

Answers (2)

Markus
Markus

Reputation: 1430

I had this problem locally, too. Elasticsearch and Kibana on local Debian 8 system. Although telnet/curl for localhost:9200 worked, I had to enable it in iptables

iptables -A INPUT -p tcp --dport 9200 -j ACCEPT

Maybe this helps someone else, too.

Upvotes: 0

avr
avr

Reputation: 4883

When you configure kibana with 

elasticsearch.url: "http://my-es-domain-xxxxxxxxxxxx.us-west-2.es.amazonaws.com‌​"

it always look for es running on 9200 port by default.

If you are running es on 80 port then explicitly mention that in configuration like this:

elasticsearch.url: "http://my-es-domain-xxxxxxxxxxxx.us-west-2.es.amazonaws.com‌​:80"

You can read more about this setting here

elasticsearch.url: Default: "http://localhost:9200" The URL of the Elasticsearch instance to use for all your queries.

Upvotes: 5

Related Questions