This is the process to deploy Apache Hadoop 2 cluster on the EC2 cloud service offered by Amazon Web Services (AWS), using Hortonworks Data Platform.
Both EC2 and HDP offer many knobs and buttons to cater to your specific, performance, security, cost, data size, data protection and other requirements. I will not discuss most of these options in this blog as the goal is to walk through one particular path of deployment to get started.
- Amazon Web Services account with the ability to launch 7 large instances of EC2 nodes.
- A Mac or a Linux machine. You could also use Windows but you will have to install additional software such as SSH clients and SCP clients, etc.
- Lastly, we assume that you have basic familiarity with EC2 to the extent that you have created EC2 instances and SSH’d in.
STEP 1: CREATING A BASE AMI WITH ALL THE OS LEVEL CONFIGURATION COMMON TO ALL NODES
Navigate to your EC2 console from the AWS Dashboard and then click on ‘Launch Instance’:
Let’s select the RHEL 64bit and go to the next step:
Let’s select a large instance with adequate processing power and memory:
Here we adjust storage as required:
We are ready for Review and Launch:
But, before you Launch the instance, make sure you have downloaded the private key. Keep the private key safe and Launch:
Everything looks good. Let’s view the instances.
Now that we have instance up and running, we will need the public DNS name to connect to it:
Let’s SSH in:
Now let’s prep the instance:
That was all the prep we need, so we are going to create a private AMI. Go to the EC2 console, select the instance and from the action menu select “Create Image”:
Make sure you check ‘No reboot’ before you click Create Image, as we will like to continue to work on this instance:
Wait for the creation of the AMI to be complete:
Let’s configure this instance for password-less SSH to all the other nodes in the cluster. The first step is to have the private key on this instance.
We will need to move the private key to .ssh folder and rename it to id_rsa:
Let’s provision the other nodes now:
Select the size of the node instances:
I will select 6 more nodes here with 3 nodes dedicated for all the management daemons and 4 nodes dedicated to data nodes. Then click on ‘Review and Launch’:
Click on the “Launch” button:
Ensure, you are using the same key as before for the passwordless SSH to work between the Ambari node and the rst of the new nodes. Click on the ‘Launch Instance’:
As the instances are getting launched, we will copy down to a text file the Private DNS names of all the instances we have launched so far:
We will end up with a list like below:
STEP 2: CUSTOMIZE THE SECURITY GROUPS TO MINIMIZE ATTACK SURFACE AREA WHILE NOT BLOCKING ESSENTIAL COMMUNICATION CHANNELS
We have have to add rules to the security groups which was created by default when we launched the instances.
The first security group should have been created when we launched the first instance. We are running the Ambari server on this instance, so we have to ensure we can get to it and it can communicate with the rest of the instances that we launched later:
Then we also need to open up the ports for IPs internal to the datacenter:
STEP 3: SETTING UP AMBARI
Get the bits of HDP and add it to the repo:
next we will refresh the repo:
Then we will install the Ambari server:
Agree to download bits:
Agree to download the key:
Ambari Server bits are installed:
Now, we will configure the bits:
Just accept all the all the default options for all the prompts by pressing Enter:
Let’s start the Ambari Server:
That’s it we are all set to use Ambari to bring up the cluster.
STEP 4: USING AMBARI TO DEPLOY THE CLUSTER
Copy the public DNS name of the Ambari:
Navigate to port 8080 of the public DNS from your browser. You should see the login page of Ambari. The default username and password is ‘admin’ and ‘admin’ respectively:
This is where we start creating the cluster. Enter any cluster name of your choosing:
We are going to create a HDP 2.0 cluster:
Remember the list of private DNS names that you had copied down to a text file. We will pull out the list and paste it in the Target host input box. We will also upload the private key that we have been using on this page:
We are all set to go. These should all come back as green with no warnings:
At this stage, we need to decide what services we need:
For this demonstration, I will select everything, although in real life you want to be more judicious and select the bare minimum needed for your requirement:
After we are done selecting the services, it’s time to determine where they will run. Ambari is smart enough to suggest you reasonable suggestions, but if you have specific topology in mind you might want move these around:
Next step is to configure which nodes do you want to Data nodes and Clients to be. I like to have clients on multiple instances just for the convenience.
In the next step we will have to configure the credentials for some of the services. the ones where you will need to populate the credentials are marked by a number in the red background mark:
Once we are done with all the inputs, we are ready to review and then start the deployment:
At this point it will take a while ( ~ 30 mins) to complete the deployment and test the services: