You can decide what goes inside the lab your students work on during the training, depending on the software you require for your course. To do that, you will have to work with a custom lab image. Creating a lab image once allows you to use it repeatedly during different training events (and event class templates, if you have more than one course which should use the same lab), removing any installation overhead from you and your students before the event begins.
Strigo’s labs run on Amazon’s cloud infrastructure and use images called AMIs
You can use two types of custom labs:
- An AMI from AWS's Marketplace
- An AMI created by you.
Using an AMI from AWS's Marketplace
Strigo allows you to utilize AWS's massive AMI selection to your benefit. Any AMI containing any type of Linux or Windows software already provided in the Marketplace can be used, as long as:
- The AMI is in the
- The AMI is public.
Note: AMIs requiring a Marketplace subscription cannot be used directly. Contact us if you want to use one.
Creating and using your own AMIs
Since we understand you will want to provide images containing your own software, we also support any other Linux or Windows AMI you provide.
There are two ways to use your own AMI:
Note that in both cases, the AMI must be in the eu-central-1 (Frankfurt) region for Strigo to be able to utilize it.
The process of creating an AMI is fairly simple:
- Launch an AWS instance using the AMI you want to be the base for your new AMI.
- Connect to it (via SSH or RDP) and modify it to your liking.
- Save it as a new AMI.
- Make public or Share with us.
To choose your custom lab as part of a class template, see Creating a class template.
Supported tmux version
Part of the Strigo lab solution consists of enabling trainers and students to collaborate on the lab from within the classroom in real-time.
To achieve that, Strigo manages SSH sessions to lab instances that have an SSH interface.
The sessions are managed with tmux, and the minimum version of tmux recommended by Strigo for a fully supported experience is 2.1. Please notice that some package managers in linux distributions install by default a tmux version lower than 2.1, so an installation of tmux not via a package manager will be required (as described here, for example).