Deploy Cluster
This workshop is using the AWS Event Engine. This will provide an account for you to carry out the activities. Please ensure that you are not logged into another account before commencing.
You will be provided with a hashcode.
https://dashboard.eventengine.run/login?hash=myhashcode
This will display the log in screen as displayed below
Click on the AWS Console button
A screen will appear with credentials and select open console
Preparing Key Pairs
In order to access the EC2 instances deployed by the lab, you need an SSH key pair. You can register a key pair for use by EC2 by following the instructions below.
Using existing SSH Key
Creating a new SSH Key with EC2
Additional Instructions for Windows
Windows - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html#putty-private-key
Deploy Cloudformation stack
Navigate to Cloudformation service in the Console. Once you click on the Create Stack button, you will be presented with the following options set.
Enter the following url in the Amazon S3 URL field and Click Next
https://s3-us-west-2.amazonaws.com/2019-opn-302-cfn/od4es.json
In the next screen, the Stack name and your ssh KeyName are parameters you need to update. The other parameters are pre-populated with default values. and you will not need to change them.
Click Next.
Leave the options blank on the Options screen and click Next.
On the Review screen, Click the check boxes to acknowledge that AWS CloudFormation might create IAM resources with custom names and contain Macros. Click Create stack.
CloudFormation will kick off the deployment of the other templates to their own stacks. It can take up to 10 minutes for the whole process to complete. You will see notations called NESTED that indicate child stacks were created by the parent template. Click the name of your stack to see the details of the creation.
When the stack is done, you will see it marked CREATE_COMPLETE. It may take another 5 minutes for the package installs and startup scripts to complete.
Access your cluster
Navigate to EC2 service and select EC2 Instances. You'll find all 7 EC2 instances that are part of your Open Distro for Elasticsearch cluster. The seed node and the client nodes have public IP address.
Use the public IP and login to one of the client nodes as user ubuntu. ( SSH from Mac/Linux Or Putty from Windows Laptops)
- On Mac - Please ensure the permissions for the local .pem file is set to 600 (
chmod 600 </path/to/your private key>) - On Windows - If you had created a pem key, please ensure you convert to ppk.
ssh -i </path/to/your private key file> ubuntu@<client-node-ip>Once logged in run the below curl command to find the status of the cluster nodes
curl -k https://localhost:9200/_cat/nodes?v -u admin:adminYou should see 7 nodes – 1 seed, 2 masters, 2 data and 2 client nodes
Access Kibana
Open your browser and navigate to http://<client-node-ip>:5601/
Login as admin ( default password - admin )