After you launch your Ryft Elasticsearch instance from the AWS EC2 cloud, verify that your instance is running properly. To do this, remotely access the Ryft Elasticsearch server using SSH, determine the status of the Elasticsearch service, and then access the Kibana application using a web browser.
- Get Public DNS Address & Key Pair/Key Name
- Remote SSH Session to Your Ryft Elasticsearch Instance
- Verify Elasticsearch Status
- Log into Kibana on your Ryft Elasticsearch Instance via Web Browser
You need the Public DNS Address and the Key Pair/Key Name for your instance.
To create an SSH session or to access the Kibana application, you need the public DNS address for your instance. Go to the EC2 dashboard, select your instance, and then copy the Public DNS Address in the "Description" tab.
In this example, the Public DNS Address is "ec2-12-34-567-890.compute-1.amazonaws.com", the IPv4 Public IP address is "12.34.567.890", and the Key Name is "f1-keypair-demo".
To verify the health of your instance, open a remote SSH session from your client computer to your Ryft Elasticsearch instance using the Public DNS address and your private Key Pair/Key Name.
When you initially created your Amazon Key Name (PKI key), it automatically defaults to a 755 file permission mode. In order to log on to your Ryft Elasticsearch instance via SSH, you must change the file permission of your PKI Key to 700, 600 or 400. You cannot allow “groups” or “others” to read, write or execute the file. Only “users” should have privileges for the PKI Key file. Use the "CHMOD 700" command to modify the permissions on the file so that only the user has the rights to read, write or execute your PKI Key.
Upon successful login, notice the “Welcome!” banner with the Elasticsearch password for the “es_admin” account. In this example, the password is "FakePsswd." Write this down so that you can authenticate and access the Kibana application.
Another way that you can verify that the Elasticsearch process is running is by using this command:
firstname.lastname@example.org:~$ sudo service Elasticsearch status | grep active
Active: active (running) since Mon 2017-08-28 21:53:26 UTC; 1 weeks 4 days ago
This tells us that Elasticsearch has been running for 1 week and 4 days.
Lastly, access Kibana, which is part of the Ryft Elasticsearch instance and is running on the AWS Elastic Cloud infrastructure, using the public DNS address with port 5601 in a web browser, like this:
Press return and Kibana begins to load.
You have to log into Kibana (authenticate) using the user ID “es_admin”, and the Elasticsearch password you saw in the SSH Welcome! banner (our example was "FakePsswd").
Once you successfully authenticate, you can access Kibana on the web and perform searches and queries.