Launch 2 instances with below attributes
You can use the AWS option to launch 2 instances.
Roost Control Plane
EaaS Server
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) |
Termination protection | Enable |
Security Group Rules |
|
Tag | Name: Roost Control Plane |
Download key-pair; change permissions to 0400
Review configuration and Launch Instance
Connect to EC2 using SSH once it is running
Mount EBS volume and fetch RoostInstaller (this step is taken care by the below command)
curl -s https://roost-stable.s3.us-west-2.amazonaws.com/enterprise/roost.sh | SETUP=1 DISK=<> CUSTOMER=<> bash -
2: EC2 Instance: Roost EAAS Server
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) |
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
|
Tag | Name: Roost EaaS Server |
Download key-pair; change permissions to 0400
Review configuration and Launch Instance
Further configuration of EaaS Server and JumpHost is enabled via the Admin page on Roost Enterprise Control Plane