Wallaroo Community AWS EC2 Setup Instructions
Setup AWS EC2 Environment for Wallaroo
The following instructions are made to assist users set up their Amazon Web Services (AWS) environment for running Wallaroo using AWS virtual servers with EC2. This allows organizations to stand a single virtual machine and used a pre-made Amazon Machine Images (AMIs) to quickly stand up an environment that can be used to install Wallaroo.
To install Wallaroo in your AWS environment based on these instructions, the following prerequisites must be met:
- Register an AWS account: https://aws.amazon.com/ and assign the proper permissions according to your organization’s needs. This must be a paid AWS account - Wallaroo will not operate on the free tier level of virtual machines.
Create the EC2 VM
To create your Wallaroo instance using a pre-made AMI:
Log into AWS cloud console.
Set the region to N. Virginia. Other regions will be added over time.
Select Services -> EC2.
Select Instances, then from the upper right hand section Launch Instances->Launch Instances.
Set the Name and any additional tags.
In Application and OS Images, enter
Wallaroo Installand press
From the search results, select Community AMIs and select Wallaroo Installer 3a.
Set the Instance Type as
c3.8xlargeas the minimum machine type. This provides 32 cores with 60 GB memory.
For Key pair (login) select one of the following:
- Select an existing Key pair name
- Select Create new key pair and set the following:
- Name: The name of the new key pair.
- Key pair type: Select either
- Private key file format: Select either
.ppk. These instructions are based on the
- Select Create key pair when complete.
Set the following for Network settings:
- Firewall: Select Create security group or select from an existing one that best fits your organization.
- Allow SSH traffic from: Set to Enabled and Anywhere 0.0.0.0/0.
- Allow HTTPs traffic from the internet: Set to Enabled.
Set the following for Configure Storage:
- Set Root volume to at least
400 GiB, type
- Set Root volume to at least
Review the Summary and verify the following:
- Number of instances: 1
- Virtual server type: Matches the minimum requirement listed above.
- Verify the other settings are accurate.
Select Launch Instance.
It is recommended to give the instance time to complete its setup process. This typically takes 20 minutes.
Verify the Setup
To verify the environment is setup for Wallaroo:
From the EC2 Dashboard, select the virtual machine created for your Wallaroo instance.
Note the Public IPv4 DNS address.
From a terminal, run
sshto connect to your virtual machine. The installation requires access to port
8800and the private key selected or created in the instructions above.
sshcommand format for connecting to your virtual machine uses the following format, replacing the
$VM_DNSwith your private key file and the DNS address to your Amazon VM:
ssh -i "$keyfile" ubuntu@$VM_DNS -L8800:localhost:8800
For example, a
Doc Sample Key.pemand
ec2-54-160-227-100.compute-1.amazonaws.comwould be as follows:
ssh -i "Doc Sample Key.pem" firstname.lastname@example.org -L8800:localhost:8800
If the Kubernetes setup is still installing, wait until complete and when prompted select EXIT to complete the process. This process may take up to 20 to 30 minutes.
With your environment ready, it’s time to install Wallaroo.
|Install Wallaroo||Install Wallaroo into a prepared environment|
Cost Saving Tips
The following tips can be used to save costs on your AWS EC2 instance.
Stop Instances When Not In Use
One cost saving measure is to stop instances when not in use. If you intend to stop an instance, register it with static IP address so when it is turned back on your services will continue to function without interruption.
I keep seeing the errors such as connect failed. Is this a problem?
Sometimes you may see an error such as
channel 3: open failed: connect failed: Connection refused. This is the ssh port forwarding attempting to connect to port 8800 during the installation, and can be ignored.
When Launching JupyterHub, I get a Server 500 error
If you shut down and restart a Wallaroo instance in a new environment or change the IP address, some settings may not be updated. Run the following command to restart the deployment process and update the settings to match the current environment:
kubectl rollout restart deployment hub