This guide will help you setup two instances of Cucumber Pro that can be interchanged and share the same data storage (EBS).
Go to the EC2 Dashboard and launch a new instance. During the launch wizard, use the following configuration:
Pick any Replicated-supported linux Amazon Machine Image (AMI). See https://help.replicated.com/docs/distributing-an-application/supported-operating-systems/. This guide was written while using
Red Hat Enterprise Linux 7.4 (HVM), SSD Volume Type - ami-c90195b0.
Choose any instance type that fits the Cucumber Pro's requirements. We have successfully tested on
t2.large but recommend
m5.xlarge as it provides the right amount of RAM and much better network performances which impact I/O.
Defaults options are fine.
Add an additional volume, next to
root of type
/dev/sdb of sufficient size (at least 20 gB, this depends mostly on the size of your project repositories). Make sure it is set to not be deleted on instance termination.
Don't select any snapshot, it is a new volume.
Optional, you can tag the instance if you want to.
Add all the firewall rules as described in Cucumber Pro's firewall instructions. If you are inside a private network, you might skip this altogether.
You can now launch the new instance! You will have to select an existing key pair or create a new one to be able to log into the instance.
SSH into the newly-created instance with the public key:
ssh -i <path/to/public.key> [email protected]<instance-ip>
Follow these instructions to format and mount the EBS volume. On RedHat, the volume was available as
/dev/xvdb. You'll need to mount the fresh ext4 partition on
You now have a machine ready to run Cucumber Pro. Follow the usual appliance setup instructions starting with installing Replicated.