-
Open the AWS Management Console.
-
Search for VPC and click the resulting link:
- Click the orange Create VPC button:
- Scroll to the bottom of the page and click the orange Create VPC button:
You will see the progress under the Create VPC workflow heading:
- Search for EMR and click the resulting link:
- Click the orange Create cluster button:
- Under the Name and applications > Amazon EMR release > Application bundle section:
- Add Tez 0.10.2 to the bundle selection.
- Under the Networking section:
- Click the Browse button next to the Create VPC button.
- Click the Refresh button at the top right:
- Select the newly created VPC, then click the orange Choose button:
You will see values similar to the following:
- Expand EC2 security groups (firewall) and set:
- EMR-managed security group (Primary node): Create ElasticMapReduce-Primary
- EMR-managed security group (Core and task nodes): Create ElasticMapReduce-Core
- Scroll down to Security configuration and EC2 key pair, then click the Create key pair button:
- Give the key a name (e.g., "hive-key"), then click the orange Create key pair button:
The generated key file (e.g., hive-key.pem) will download automatically.
- Return to the previous window and click the Browse button next to the Create key pair button:
- Click the Refresh button at the top right, select the generated key pair, and click the orange Choose button:
You will see the name of the selected key pair:
- Under the Identity and Access Management (IAM) roles section:
- Select Create a service role. You will see the default values pre-selected:
- Under the EC2 instance profile for Amazon EMR section:
- Select Create an instance profile:
- Finally, at the bottom right, click the orange Create cluster button:
After a while, you will see a success message indicating the cluster has been created:
- Scroll down to the Network and security section:
- Expand EC2 security groups (firewall).
- Click the link below Primary node EMR managed security group:
- Expand EC2 security groups (firewall).
- In the newly opened tab, click Edit inbound rules under the Inbound rules section:
- In the new window, click the Add rule button at the bottom left:
- Click the first dropdown menu and type (or select) SSH:
- Click the second dropdown menu and select My IP:
- Click the orange Save rules button at the bottom right:
- Return to the EMR window and click the Refresh button at the top right. You should see the cluster's Status change to Waiting:
- Before connecting to the cluster, ensure the key file has the correct permissions. Locate the
hive-key.pemfile (usually in yourDownloadsfolder, not your home folder) and set the appropriate permissions:
% chmod 400 hive-key.pem- Return to your browser and click the Connect to the Primary node using SSH link under the Primary node public DNS heading. You will see instructions on how to connect to your newly created cluster:
- Copy the command and paste it into your terminal. Before executing it, ensure the path to your
hive-key.pemfile is correct:
% ssh -i ~/hive-key.pem hadoop@**************************.amazonaws.comYou will see the fingerprint message:
The authenticity of host '**************************.amazonaws.com (************)' can't be established.
ED25519 key fingerprint is: SHA256:*******************************************
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? - Type
yesand press Enter.
Finally, you will access the SSH shell for your cluster:
** WARNING: connection is not using a post-quantum key exchange algorithm.
** This session may be vulnerable to "store now, decrypt later" attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html
, #_
~\_ ####_ Amazon Linux 2023
~~ \_#####\
~~ \###|
~~ \#/ ___ https://aws.amazon.com/linux/amazon-linux-2023
~~ V~' '->
~~~ /
~~._. _/
_/ _/
_/m/'
Last login: ************************
EEEEEEEEEEEEEEEEEEEE MMMMMMMM MMMMMMMM RRRRRRRRRRRRRRR
E::::::::::::::::::E M:::::::M M:::::::M R::::::::::::::R
EE:::::EEEEEEEEE:::E M::::::::M M::::::::M R:::::RRRRRR:::::R
E::::E EEEEE M:::::::::M M:::::::::M RR::::R R::::R
E::::E M::::::M:::M M:::M::::::M R:::R R::::R
E:::::EEEEEEEEEE M:::::M M:::M M:::M M:::::M R:::RRRRRR:::::R
E::::::::::::::E M:::::M M:::M:::M M:::::M R:::::::::::RR
E:::::EEEEEEEEEE M:::::M M:::::M M:::::M R:::RRRRRR::::R
E::::E M:::::M M:::M M:::::M R:::R R::::R
E::::E EEEEE M:::::M MMM M:::::M R:::R R::::R
EE:::::EEEEEEEE::::E M:::::M M:::::M R:::R R::::R
E::::::::::::::::::E M:::::M M:::::M RR::::R R::::R
EEEEEEEEEEEEEEEEEEEE MMMMMMM MMMMMMM RRRRRRR RRRRRR
[hadoop@************* ~]$



























