MidVision RapidDeploy on AWS

Amazon EC2 Installation and Support Guide

This guide will provide step by step instructions how to start using the installed products on your AWS EC2 instance.

1. Launching and accessing the instance

1.1 Launching an instance

In order to launch MidVision RapidDeploy (sometimes referred as RD), a few settings need to be configured on the AWS console as follows:
  1. Select the AMI based on your requirements;
  2. Right click on the AMI, or from the drop down menu, choose the ‘Launch’ option;
  3. Choose the instance type. The M3.medium type or larger is recommended when running RapidDeploy. Larger instances may be required based on the number of projects and deployments etc required and the expected resource use of each;
  4. Specify the security group. The security group needs to permit to following ports:
Port 22 to connect via SSH (enabled by default), 
Port 9090 to reach RapidDeploy web console, 
Port 20000 and 20100 to open for RapidDeploy Remote Agent (optional),
FAST PATH: Specify a security group that opens all TCP ports from Anywhere

1.2 Logging into the instance

Once the instance has started up (you can see it by having " 2/2 checks passed " in EC2 console), you can connect by clicking " Connect " button on EC2 console instances section and following the instructions . You can log in to your instance with username  " midvision ", using the previously (instance launch-time) selected .pem keyfile.

2. Getting started with RapidDeploy

2.1 Changing RapidDeploy initial password

For security reasons, you will need to change the default password for user mvadmin. This will be requested the first time only when you log in to the instance. Be carefull because if you choose default option the password will be changed into instance-id

2.2 RapidDeploy server

RapidDeploy server and agent will start up automatically when you start your instance. You can access the web console onhttp://[publicip]:9090/MidVision Note: make sure you have port 9090 open in your Security group when trying to access RapidDeploy web console. For the first time, you can set the password for the default username "mvadmin". You can prevent auto starting RapidDeploy on instance startup by removing it from the system chkconfig list. 

[midvision@ ] sudo chkconfig --del rapiddeploy

3. Users, files, scripts and technical info

3.1 Users

  • midvision: This is the default user, which you can log in as. It is permitted to use all SUDO rights. To switch to the root user, type "sudo su".
  • root:      This is the superuser in linux systems. You can log in as any other user without using passwords. E.g: "su ec2-user", "su midvision"
  • ec2-user:  This user does not have SUDO rights. If you want to switch back to root user, type "exit", this will take you back to the previous user session.

3.2 Provided post-install scripts

Scripts are provided in the midvision home directory, as detailed in the following sections:

3.2.1 Opening Red Hat Entreprise Linux firewall with the open-firewall.sh script

RHEL instances are shipped with a firewall by default to protect your machine. For security reasons, the instance is only accessible via SSH (port 22) at first, so further ports can be opened on the firewall as needed. You will need to open all the ports in this internal firewall, which you have open in your Security group. There is a script placed in the user home of midvision (/home/midvision), which is also the starting location when logged in. You will need to be the root user to run this script. Example usage:
[midvision@ ] sudo ./open-firewall.sh 9090 
Open firewall port 9090 iptables: 
Saving firewall rules to /etc/sysconfig/iptables:[ OK ]

3.3 Starting and stopping RapidDeploy manually

To restart RapidDeploy manually from the filesystem, use the rapiddeploy linux service. The RapidDeploy version is 4.0.7. RapidDeploy home is located at /var/rd/midvision Example usage:
[midvision@ ] sudo service rapiddeploy start
[midvision@ ] sudo service rapiddeploy stop 
The RapidDeploy server uses an in-memory database, so your RapidDeploy framework needs to be shut down properly to save your work. This happens when the instance is stopping or when calling the stop service manually from the command line. Note that on instance restart, unsaved data will be lost.

3.4 Files used for DevTestCloud services

There are a few scripts and other files in midvision and root users home directory, which will need to remain unchanged in order to keep the provided scripts working. There are a set of scripts in midvision home directory. Those scripts are executed when logging into the instance controlled by .bash_profile, but you can also execute them manually whenever they are needed. There are some hidden files used as well,.firstRun indicates that the setup wizard has already run once.

4.0 Troubleshooting

4.1 Session loss during setup

If you lose your SSH connection to the target instance during the first run setup script execution (e.g. as a result of a network problem), we advise you to delete and recreate the EC2 instance and run the script again.

4.2 Contacting MidVision support

Please visit our  support website.

Documentation

RapidDeploy 4.0 Documentation.

'Get Started' Webcasts

RapidDeploy 4.0 on YouTube.

'How To' Webcasts

RapidDeploy 4.0 on YouTube.