Amazon EC2 Installation guide

1. Overview

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

This AMI contains a ready-to-run MidVision RapidDeploy for Database Server (Win) on AWS base image at the selected version.

In order to use this image, you need to launch it with your selected type and log in using remote desktop.

Visit the MidVision RapidDeploy for Database Server (Win) pages on the AWS Marketplace

2. Launching an instance

In order to launch MidVision RapidDeploy for Database Server on Windows, a few settings need to be configured on the AWS console as follows. The instructions for launching an instance differ depending on where you launch from. Initially, you will launch the instance from the AWS Marketplace.

From the AWS Marketplace

From the AWS EC2 Control Panel

From the AWS Marketplace

Select the Product based on your requirements in the AWS Marketplace;
Click on the link to go to that versions page in AWS Marketplace;
Check the ‘Other Versions ‘ link to see other versions available (you can select the actual version later).
Under ‘Pricing Details‘ panel select your Region and either Hourly or Yearly fees.
Click on the ‘Continue‘, button to go to the ‘1-Click Launch‘ tab on the configuration page;
On the ‘Software Pricing‘ panel choose your instance type and pricing type;
On the ‘Version‘ panel, select the fix pack version you require;
On the ‘Region‘ panel, select the Region you require;
On the ‘EC2 Instance Type‘ panel, choose the instance type. The m3.large type or larger is recommended when you expect your database will need more resources;
On the ‘VPC Settings‘ panel Configure the VPC settings to your requirements or leave the defaults;
On the ‘Security Group‘ panel, specify the security group. The security group needs to permit to following ports [note that the internal firewall will be configured later to permit only ports used by DB2]:
```
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)
```
- If you don’t already have a security group as above, go to your EC2 Control Panel and select ‘Security Groups‘ under ‘Network & Security‘
- Click ‘Create Security Group‘ button
- To open all ports, Click ‘Add Rule‘.
- In the ‘Type‘ dropdown, Specify ‘All TCP‘ or your preferred configuration.
- In the ‘Source‘ dropdown, Specify ‘Anywhere‘ or your preferred configuration.
On the ‘Key Pair‘ panel, select a key pair to use. You will need this key later to connect to the instance.
Scroll back to the top of the page and click ‘Accept Software Terms and Launch with 1-Click‘.
The instance will be launched.

From the AWS EC2 Control Panel

Select the AMI based on your requirements;
Right click on the AMI, or from the drop down menu, choose the ‘Launch’ option;
On the ‘Choose Instance Type‘ tab, choose the instance type. The m3.large type or larger is recommended when you expect your database will need more resources; Click ‘Next: Configure Instance Details‘.
On the ‘Configure Instance‘ tab Configure the instance to your requirements or leave the defaults. Click ‘Next: Add Storage‘.
On the ‘Add Storage‘ tab, add additional storage as required or leave as default. Click ‘Next: Tag Instance‘.
On the ‘Tag Instance‘ tab, Tag your instance with a suitable name. Click ‘Next: Configure Security Group'.
On the ‘Configure Security Group‘ tab, 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)
```
- To open all ports, Click ‘Add Rule‘.
- In the ‘Type‘ dropdown, Specify ‘All TCP‘ or your preferred configuration.
- In the ‘Source‘ dropdown, Specify ‘Anywhere‘ or your preferred configuration.
Click ‘Review and Launch‘.
Review settings, then click ‘Launch‘.
Add your key pair, Check the ‘Acknowledge key file access’ checkbox and click ‘Launch Instance‘.

3. Initial login and setup

The products are shipped without any initial configuration so you can create your own databases and configure it to meet your requirements.

Once the instance has started up (you can see it by having ” 2/2 checks passed ” in EC2 console).

Log onto the instance using a remote desktop application:
- From the EC2 console select the instance and click on the “Connect” button, click on the “Get Password” button, browse and select the key pair .pem file, click on the “Decrypt Password” button, and use the generated password to connect to the instance using the desired remote desktop application.

IMPORTANT!

Remember you need to have the necessary rules in the Windows firewall to access the DB2 ports if necessary. In order to do this:

1. Open the tool “Windows Firewall with Advanced Security” in Windows

2. Select “Inbound rules“

3. Click on “New Rule...“

4. Select “Port” and click “Next“

5. Select “TCP” and set the “Specific local ports” to the necessary specific port values, by default it should be something like “9090,50000“, and click “Next“

6. You can leave the rest of the values by default on the following windows and assign a memorable name to the rule

4. Accessing the web consoles

IMPORTANT!

Before you access web console you will need to run script to change the passwords into your unique ‘[instance-id]‘

1. Create an empty file C:\firstrun.txt

2. Open Powershell console

3. Go to “C:\rd\scripts”

4. Run changePasswords.ps1 script

Now your password for db2admin user and RapidDeploy web console is set to ‘[instance-id]‘

4.1 Access the RapidDeploy Web Console

RapidDeploy server and agent will start up automatically when you start your instance. You can access the web console on:

http://[publicip]:9090/MidVision

Note: make sure you have port 9090 open in your Security group when trying to access RapidDeploy web console. You can log in with the administrative user ” mvadmin ” using your ‘[instance-id]‘ as password.

4.2 Access DB2 installation

You can find your DB2 installation under:

C:\IBM\SQLLIB

Note: During DB2 installation a new user ” db2admin ” has been created. Log in to the instance as Administrator first and the password for db2admin user will be automatically set to ‘[instance-id]‘ .

5. Maintaining the installation

The following sections cover some of the activities you might want to perform after the instance has been started.

Changing RapidDeploy initial password

For security reasons, you will need to change the default password (default value is ‘[instance-id]‘) for user mvadmin. You can change this password at any time by clicking the ‘mvadmin’ drop down in the top right hand corner and clicking ‘Change Password’.

6. Troubleshooting

6.1 Session loss during setup

If you lose the 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.

6.3 Contacting MidVision support

Please visit our support website.