I installed ECE on an AWS EC2 instance, and it bootstrapped fine. Then I created a cluster, success. Then I enabled Kibana on the cluster. How do I access Kibana now? To access the admin console, I opened up a port using SG, and whitelisting my IP. But for Kibana, all I see is an internal IP address, what is the port I am supposed to hit?
Thanks Yuri, that helped a little. Reading the documentation, I was able to figure out that the internal port for that Kibana is 9243. Now, I am running on an EC2 instance, and as I mentioned I opened ports to my IP. Based on that, I hit this URL:
After accepting some warnings about certs, the page loads, but I get:
Surely this is not an unusual case where someone is trying ECE install for the first time on an AWS EC2 instance? I was really hoping for a How-To guide specific to AWS EC2.
The Platform settings page has this to tell me:
"Specify a CNAME that replaces the default hostname. This CNAME is used to modify your cluster and Kibana endpoints."
Could you please help me understand what that means, and how it gets me to "I want to hit the Kibana that I just provisioned, from outside EC2, which of course is the only way to run a browser"
Sorry for the newbie questions.
Sorry to answer my own question, but I guess you can take this as feedback on the documentation.
This is what I had to do to finally get Kibana to load on ECE that is running on AWS EC2 instance. Perhaps you can add that info in the docs somewheres:
- First open up ports as needed by looking at the endpoints page (in my case 9243)
- Then go to Platform->Settings page and replace the InternalIpAddress.ip.es.io CNAME with PublicIpAddress.ip.es.io and hit submit
Now Kibana will load since the magic underneath will then resolve it correctly to the public IP address, so you can hit it from the browser. This information is (sort of) derivable from the documentation provided here:
Note that this is "plan your deployment" documentation. Typically not what n00bs will read on day one!
Specifically the paragraph below. But it would so cool if y'all can remove a bunch of RTFM type conversations and reduce the friction for first-use of ECE, by just adding that small tip ahead of time (assuming of course that my tip is generally valid).
"By default, Elastic Cloud Enterprise uses the external ip.es.io service provided by Elastic to resolve virtual cluster host names in compliance with RFC1918. The service works by resolving host names of the form .ip.es.io to . In the case of Elastic Cloud Enterprise, each cluster is assigned a virtual host name of the form ..ip.es.io:, such as https://6dfc65aae62341e18a8b7692dcc9722.214.171.124.132.ip.es.io:9243. The ip.es.io service simply resolves the virtual host name of the cluster to the proxy address which is specified during installation, 10.8.156.132 in our example, so that client requests are sent to the proxy. The proxy then extracts the cluster ID from the virtual host name of the cluster and uses its internal routing table to route the request to the right allocator."
I am happy you were able to solve the problem and thank you for the feedback, it is valuable for us. We will improve the documentation.
Would the steps in https://www.elastic.co/guide/en/cloud-enterprise/current/ece-aws-private-ip.html have helped you? I added this to the documentation based on my own experiences with AWS.
ha!! Yes, exactly what I ran into and would have totally helped!!
But on the bright side, I RTFM.
I think the issue here might be that we need to make the information that would have helped easier to find. We will add a link to https://www.elastic.co/guide/en/cloud-enterprise/current/ece-administering-endpoints.html.
Good feedback, thank you!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.