5. EC2 Instance Setup

Launch 2 instances with below attributes

You can use the AWS option to launch 2 instances.

1. EC2 Instance: Roost Control Plane

Below configuration is good for 2-3 team size

Attribute	Selection
AMI	Choose Ubuntu 20 (ubuntu-focal-20.04) SSD Volume Type
Instance Type	c5.2xlarge or bigger in CPU & memory Shutdown behaviour (Stop) Enable Termination Protection
Storage	Root Volume: 30GB (gp3) EBS: 100GB (gp3) (Disable Delete on termination)
Termination protection	Enable
Security Group Rules	SSH (port 22) HTTPS (port 443)
Tag	Name: Roost Control Plane

Similar to EC2 Instance 1 with few changes

Use the tags to give a different “Name” like “Roost EAAS Server” for ease of identification

This instance will also act as the default “JumpHost” for user managed clusters. Optionally, it can host a Docker Host and Docker Insecure Registry.

Attribute	Selection
AMI	Choose Ubuntu 20 (ubuntu-focal-20.04) SSD Volume Type
Instance Type	c5.2xlarge or bigger in CPU & memory Shutdown behaviour (Stop) Enable Termination Protection
Storage	Root Volume: 30GB (gp3) EBS: 100GB (gp3) ( Disable Delete on termination)
Termination protection	Enable
Security Group Rules	Please note if Controlplane and EaaS Server are in the same VPC, then we can use just Private IP and configure “All TCP” from security-group of the controlplane If this instance is in a different region/VPC then we have to enable Public/External IP and open below traffic from anywhere SSH (port 22) HTTPS (port 443) TCP Port 5000 for Docker Host TCP Port 5002 for Docker Insecure Registry TCP Port 60001 for Jump Host RoostApi Server TCP Port 60002 for Roost Cluster Launcher TCP Port 60003 for EaaS API Server TCP Port 60005 for Cypress Video Server TCP Port 60006 for Web-console(gotty) default service - ubuntu user TCP Port 62020-62120 for dynamic gotty ports - mapped to individual users
Tag	Name: Roost EaaS Server

Further configuration of EaaS Server and JumpHost is enabled via the Admin page on Roost Enterprise Control Plane