CODEWITHSUNDEEP
amazon-web-serviceselasticsearchamazon-ec2kibana
Tub
Tub

Reputation: 47

AWS ElasticSearch as a Service fails to connect via standalone KIBANA

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.

However when i change Kibana.yml to point to the endpoint from ES AWS Service it turns RED.

AWS ES Endpoint Successful call from the said EC2 where standalone KIBANA is installed

{
    "name" : "BBXYZ",
    "cluster_name" : "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
    "cluster_uuid" : "XXXXXXXXXXXXXXXXXXXXX",
    "version" : {
    "number" : "6.0.1",
    "build_hash" : "d951bbf",
    "build_date" : "2017-12-07T01:43:54.348Z",
    "build_snapshot" : false,
    "lucene_version" : "7.0.1",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
    },
    "tagline" : "You Know, for Search"
}

Kibana Version 6.1.2

Kibana Error : Status Red plugin:[email protected]  Request Timeout after 3000ms

Please help; do i need to have KIBANA AND AWS ES ON THE SAME VERSION. AWS ES IS ON 6.0

The reason why ui am installing standalone KIBANA is because we want to enable login and disable actions on the KIBANA for few

Upvotes: 1

Views: 1306

Answers (1)

Vaisakh PS
Vaisakh PS

Reputation: 1201

@Tub As per the AWS documentation to connect a standalone Kibana server to Amazon ElasticSearch you need to add the http prefix and explicitly specify port 80. For example elasticsearch_url: "http://elasticsearch_domain_endpoint:80".

For more please Refer here Connecting a Local Kibana Server to Amazon ES

Upvotes: 1

Related Questions